Skip to content

fix: regenerate pnpm-lock.yaml with pnpm v8#88

Merged
JohnMcLear merged 1 commit intomainfrom
fix/lockfile-pnpm8
Apr 7, 2026
Merged

fix: regenerate pnpm-lock.yaml with pnpm v8#88
JohnMcLear merged 1 commit intomainfrom
fix/lockfile-pnpm8

Conversation

@JohnMcLear
Copy link
Copy Markdown
Member

Summary

The CI workflows use pnpm v8 (pnpm/action-setup@v5 with version: 8), which produces lockfile v6.0. The previous regen used pnpm 10 (lockfile v9.0), which pnpm 8 couldn't read cleanly — install would rewrite it, leaving the tree dirty and breaking pnpm version patch in the publish workflow.

🤖 Generated with Claude Code

The CI workflows pin pnpm/action-setup@v5 with version: 8, which uses
lockfile format v6.0. The previous regen used pnpm 10 producing v9.0,
which pnpm 8 in CI couldn't read cleanly — pnpm install would rewrite
the lockfile, leaving the working tree dirty and breaking
'pnpm version patch' in the publish workflow.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@JohnMcLear JohnMcLear merged commit bef6317 into main Apr 7, 2026
3 checks passed
@JohnMcLear JohnMcLear deleted the fix/lockfile-pnpm8 branch April 7, 2026 14:44
Sign up for free to 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.

1 participant