Migrate pnpm version management to Corepack and upgrade to pnpm 11#26
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Replaces Volta's pnpm pinning with Corepack, which is the correct mechanism for per-project pnpm version management. Also upgrades pnpm from 10.x to 11. Mirrors the approach taken in Loungebird/Backend#175 and Loungebird/Backend#176.
Changes
package.json: UpdatedpackageManagerfield topnpm@11.1.2with sha512 integrity hash (required for Corepack verification)package.json: Removedvolta.pnpm— Volta now manages Node only; Corepack manages pnpmpnpm-workspace.yaml: Added withallowBuilds: esbuild: true— pnpm 11 blocks build scripts by default; esbuild requires its postinstall script to runpnpm-lock.yaml: Updated for pnpm 11The GitHub Actions workflow already uses
pnpm/action-setup@v6without a pinnedversion:, so it will automatically read from thepackageManagerfield — no workflow changes needed.Testing
pnpm installcompletes without errorspnpm run buildproduces a clean production build