chore(repo): upgrade pnpm baseline to 12.2.1 - #434
Merged
Conversation
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.
Scope
packages/cdn-*orpackages/lib-*; publish workflow change is limited to the explicitly requested pnpm setup version;apps/**change is limited to the acceptance runner's pinned pnpm command.[email protected]withpnpm 12.x;emp doctorvalidates pnpm 12.pnpm 12 migration boundaries
ignoredBuiltDependenciesto explicitallowBuilds: false, preserving the existing denied build-script set under pnpm 12's strict dependency-build policy.@rstest/[email protected]and@rstest/[email protected]are exempted with exact selectors.pmOnFail: ignoreso pnpm 12 does not prepend an environment lockfile document that hides the real dependency graph from single-document scanners. CI, release guards, doctor, templates, and tests still enforce the 12.2.1 / 12.x baseline.pnpm-lock.yamlremains byte-identical and single-document after a frozen pnpm 12 install.Directory Boundary Check
apps/**changes are limited to the acceptance contract required by this package-manager migration.packages/cdn-*orpackages/lib-*version lines.Validation
corepack pnpm install --frozen-lockfilewith pnpm 12.2.1; lockfile hash unchanged and supply-chain policy passed.corepack pnpm workflow:checkgit diff --checkcorepack pnpm test:rules— 6 files, 51/51 tests.corepack pnpm --silent deps:core:check -- --format json— 14/14 CURRENT.corepack pnpm ci:verifycorepack pnpm empbuildcorepack pnpm apps:acceptance— 14/14 app builds and library-output smoke passed.Release Safety
NODE_AUTH_TOKEN,npm publish, orrelease:publish.apps/**andwebsite/**.corepack pnpm release:publish:dry -- --skip-buildpassed for the 17 core packages.Review