Skip to content

fix: replace pnpm/action-setup@v6 with corepack in all CI workflows - #1122

Merged
hotlong merged 2 commits into
mainfrom
copilot/fix-issue-with-recent-changes
Apr 13, 2026
Merged

fix: replace pnpm/action-setup@v6 with corepack in all CI workflows#1122
hotlong merged 2 commits into
mainfrom
copilot/fix-issue-with-recent-changes

Conversation

CopilotAI commented Apr 13, 2026

Copy link
Copy Markdown
Contributor

All CI jobs fail with ERR_PNPM_BROKEN_LOCKFILE: "expected a single document in the stream, but found more" since PR #1117 merge. The lockfile content is valid (verified with the exact @zkochan/js-yaml@0.0.11 parser bundled in pnpm 10.31.0), and pnpm install --frozen-lockfile succeeds locally. The issue is pnpm/action-setup@v6's npm-based self-installer producing a pnpm environment that misparses the lockfile.

Changes

  • Replace pnpm/action-setup@v6corepack enable across all 5 workflows (ci.yml, lint.yml, release.yml, validate-deps.yml, pr-automation.yml). Corepack uses the packageManager field in package.json with SHA-512 verification — identical binary to local dev.

  • Add pnpm --version step after corepack enable for CI debuggability.

  • Bump pnpm store cache keysv2v3 to avoid restoring stale caches from the old setup.

  • Regenerate pnpm-lock.yaml from scratch (rm + pnpm install) for a clean baseline.

Before/After

# Before
- name: Install pnpmuses: pnpm/action-setup@v6# After
- name: Enable Corepackrun: corepack enable
- name: Verify pnpm versionrun: pnpm --version

CopilotAIand others added 2 commits April 13, 2026 12:50
…o fix ERR_PNPM_BROKEN_LOCKFILE
Agent-Logs-Url: https://github.com/objectstack-ai/framework/sessions/d0e206fc-2b0c-43f9-b31d-f37a660851c9
Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
@vercel

vercelBot commented Apr 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
objectstack-playReadyReadyPreview, CommentApr 13, 2026 1:03pm
specReadyReadyPreview, CommentApr 13, 2026 1:03pm

Request Review

CopilotAI review requested due to automatic review settings April 13, 2026 13:03
@hotlong
hotlong merged commit 3ffc893 into mainApr 13, 2026
3 checks passed

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates GitHub Actions workflows to install pnpm via Corepack (using the packageManager field in package.json) and bumps the pnpm store cache key version to avoid stale caches, aiming to resolve CI failures related to ERR_PNPM_BROKEN_LOCKFILE.

Changes:

  • Replaced pnpm/action-setup@v6 with corepack enable across CI workflows.
  • Added pnpm --version verification steps (in most workflows) for easier CI debugging.
  • Bumped pnpm store cache keys from v2 to v3 and documented the CI change in the changelog.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
FileDescription
CHANGELOG.mdDocuments the CI move from pnpm/action-setup@v6 to Corepack and the cache key bump.
.github/workflows/ci.ymlSwitches pnpm installation to Corepack, adds pnpm --version, bumps cache key to v3 across CI jobs.
.github/workflows/lint.ymlSwitches pnpm installation to Corepack, adds pnpm --version, bumps cache key to v3.
.github/workflows/release.ymlSwitches pnpm installation to Corepack, adds pnpm --version, bumps cache key to v3.
.github/workflows/validate-deps.ymlSwitches pnpm installation to Corepack, adds pnpm --version, bumps cache key to v3.
.github/workflows/pr-automation.ymlSwitches pnpm installation to Corepack (but currently lacks the pnpm --version step used elsewhere).

Comment on lines +68 to 72
- name: Enable Corepack
run: corepack enable

- name: Install dependencies
run: pnpm install --frozen-lockfile
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@hotlong