Repository navigation
Move to pnpm 12 - #306
Merged
Merged
Move to pnpm 12#306
Conversation
packageManager pins pnpm 12.16.1. CI (pnpm/action-setup) and the deploy read the version from there; on the server the global pnpm 11 switches to the pinned version by itself (checked as the deploy user), so nothing has to be installed there. pnpm 12 records the pinned package manager in a packageManagerDependencies document at the top of pnpm-lock.yaml; the rest of the lockfile is unchanged, and a frozen install passes the supply-chain policies. None of the v12 breaking changes apply: pnpm-workspace.yaml only has packages, allowBuilds and overrides, and no workflow passes --frozen-lockfile false.
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
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.
What
packageManager:pnpm@12.16.1(with integrity). CI (pnpm/action-setup@v6) anddeploy.ymltake the version from there.pnpm-lock.yaml: pnpm 12 adds apackageManagerDependenciesdocument at the top that records the pinned pnpm. The dependency part is unchanged.docs/development.mdsay pnpm 12.Why it's safe
pnpm-workspace.yamlonly haspackages,allowBuildsandoverrides(unknown keys now fail the install), and no workflow uses--frozen-lockfile false.CI=true pnpm install --frozen-lockfilewith 12.16.1: done, lockfile passes the supply-chain policies, no warnings.