chore(deps): upgrade to pnpm 11 and harden supply-chain config - #15
Merged
Conversation
- Bump packageManager pnpm 10.25.0 -> 11.3.0; require Node >= 22.13 - Move pnpm settings from .npmrc into pnpm-workspace.yaml (v11 only reads auth/registry from .npmrc); .npmrc held only the moved setting, so remove it - Add supply-chain policies: minimumReleaseAge (10d), trustPolicy no-downgrade, blockExoticSubdeps - trustPolicyExclude: undici-types (known-benign provenance gap, nodejs/undici#4666) - allowBuilds: esbuild (fetches platform binary via tsx; replaces onlyBuiltDependencies) Part of PE-1866.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR upgrades the repo’s package manager to pnpm@11.3.0 and migrates supply-chain hardening configuration away from .npmrc into pnpm-workspace.yaml, aligning with pnpm v11’s configuration model.
Changes:
- Bump
packageManagertopnpm@11.3.0and declare a Node engine floor (>=22.13) inpackage.json. - Remove
.npmrcand migrate the priorminimum-release-agesetting intopnpm-workspace.yaml. - Enable pnpm v11 supply-chain protections (minimum release age, provenance downgrade protections, exotic subdependency blocking) and allow builds for
esbuild.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pnpm-workspace.yaml | Adds pnpm v11 config and supply-chain hardening policies, including build-script allowlist. |
| package.json | Updates pnpm version and sets Node engine floor required by pnpm v11. |
| .npmrc | Removes the old pnpm setting now migrated to pnpm-workspace.yaml. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
lucas-ethena
approved these changes
Jun 1, 2026
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
Upgrade pnpm
10.25.0→11.3.0and migrate to pnpm v11's supply-chain hardening model. First of a fleet-wide rollout (PE-1866).Why
pnpm v11 only reads auth/registry settings from
.npmrc— every other pnpm setting must move topnpm-workspace.yaml. v11 also ships supply-chain protections we want enabled. This PR migrates config and turns on those protections.Changes
packageManager:pnpm@10.25.0→pnpm@11.3.0; addengines.node: ">=22.13"(pnpm 11 floor).npmrc— it held onlyminimum-release-age, now migratedpnpm-workspace.yamlsupply-chain policies:minimumReleaseAge: 14400(10 days) — refuse versions younger than 10dtrustPolicy: no-downgrade— fail on publisher-trust/provenance downgradesblockExoticSubdeps: true— transitive deps must resolve from the registrytrustPolicyExclude: [undici-types]— reviewed, known-benign provenance gap (nodejs/undici#4666); without it@types/nodeblocks every installallowBuilds: { esbuild: true }— v11 replacesonlyBuiltDependencies; esbuild fetches its platform binary (viatsx)Test plan
pnpm installunder pnpm 11.3.0 / Node 22.22 succeeds; lockfile unchanged (still v9.0); esbuild postinstall runsSecurity & Data Impact
Security impact: Strengthens supply-chain posture — install-time version quarantine, provenance-downgrade detection, registry-only transitive deps. The one
trustPolicyExcludeentry is a vetted known-benign provenance gap, not a blanket bypass.Data classification affected: None.
Audit log updated: N/A.
Rollback
Revert commit — no state migration (re-pins pnpm 10.25.0).