Skip to content

chore: migrate to pnpm 11#36

Open
fhp wants to merge 2 commits into
mainfrom
pf-3332-migrate-to-pnpm-11
Open

chore: migrate to pnpm 11#36
fhp wants to merge 2 commits into
mainfrom
pf-3332-migrate-to-pnpm-11

Conversation

@fhp

@fhp fhp commented Jul 16, 2026

Copy link
Copy Markdown
Member

Summary

  • Refreshed .github/jsonnet and regenerated .github/workflows/ from upstream lib-jsonnet (actions/checkout v6 -> v7, pnpm/action-setup v5 -> v6.0.9, new GIT_VERSION)
  • Bumped packageManager to pnpm@11.13.0 in package.json
  • Added pnpm-workspace.yaml with allowBuilds to approve the core-js and highlight.js postinstall scripts, which pnpm 11 now blocks by default (previously just a non-fatal warning under pnpm 10)
  • pnpm-lock.yaml regenerated via pnpm install; no dependency changes (already lockfile v9.0, compatible with pnpm 11)

Linear: PF-3332

🤖 Generated with Claude Code

fhp and others added 2 commits July 16, 2026 16:43
- Refresh .github jsonnet/workflows from upstream (actions/checkout v6 -> v7,
  pnpm/action-setup v5 -> v6.0.9)
- Bump packageManager to pnpm@11.13.0 in package.json
- Add pnpm-workspace.yaml with allowBuilds to approve core-js and
  highlight.js postinstall scripts (required under pnpm 11's stricter
  build-script approval; previously only a non-fatal warning under pnpm 10)
- pnpm-lock.yaml unchanged (already lockfile v9.0, compatible with pnpm 11)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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