chore(deps): bump Node 22 → 24 LTS + pnpm 9.15.0 → 11.1.1#183
Merged
Conversation
Closes #175. Bundled bump (paired by necessity: pnpm 9 does not officially support Node 24). - `packageManager: pnpm@11.1.1` in root package.json. Corepack picks it up automatically; CI's pnpm/action-setup@v6.0.3 respects the field. - `node-version: 24` in all four workflows (ci, deploy-site, release, sync-law). - `pnpm-workspace.yaml` gains an `allowBuilds:` block whitelisting `esbuild` and `sharp` postinstall scripts. pnpm 11 blocks postinstall scripts by default unless explicitly approved; these two are legitimately required (esbuild downloads its platform binary, sharp selects its prebuilt for the runtime). Lockfile fully regenerated under pnpm 11. Verified locally on Node 22.22.0 + pnpm 11.1.1 (the Node 24 part is verified by CI): - pnpm install: clean, no peer-dep errors - pnpm build: all 8 packages - pnpm test: 267 passing - pnpm typecheck: 0 errors, 0 warnings - pnpm lint: clean Node 22 stays in Maintenance LTS until 2027-04, so this isn't urgent, but Node 24 is the current active LTS line ("Krypton"). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #175. Coupled bump (pnpm 9 does not officially support Node 24).
Changes
packageManager: pnpm@11.1.1in rootpackage.json. Corepack auto-installs.node-version: 24in all four workflows:ci.yml,deploy-site.yml,release.yml,sync-law.yml.allowBuilds:block inpnpm-workspace.yamlwhitelistingesbuild+sharppostinstall scripts. pnpm 11 blocks postinstall scripts by default; these two are legitimate (esbuild downloads its platform binary, sharp selects its prebuilt for the runtime).Local verification (Node 22 + pnpm 11.1.1)
pnpm install— clean, no peer-dep errorspnpm build— all 8 packagespnpm test— 267 passingpnpm typecheck— cleanpnpm lint— cleanWhat CI verifies that local can't
actions/setup-node@v6.4.0withnode-version: 24which is the real test).Rollback
If anything breaks, revert this commit — the prior state (Node 22 + pnpm 9.15.0) is the known-good baseline.
🤖 Generated with Claude Code