chore: upgrade pnpm to v11 and add minimumReleaseAge#265
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
HugoRCD
changed the title
commit: |
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
Two related changes to harden the supply chain and modernize the package manager setup.
1. Upgrade pnpm to v11
packageManagertopnpm@11.1.3version: 10.33.4frompnpm/action-setupworkflows — the action now readspackageManagerfrompackage.json(single source of truth)onlyBuiltDependencies+ignoredBuiltDependencies→ unifiedallowBuildsmap (required in v11)overridesfrompackage.json→pnpm-workspace.yaml(thepnpmfield inpackage.jsonis no longer recognized in v11)shamefullyHoist,strictPeerDependenciesfrom.npmrc→pnpm-workspace.yaml(in v11,.npmrconly holds auth/registry).npmrc(now empty)2. Add
minimumReleaseAgeto harden supply chainSets a 2-day minimum age (2880 minutes) before any newly published dependency can resolve. Mitigates compromised-package attacks where a malicious version is pushed and pulled into installs within hours.
Trusted-source allowlist exempts the Nuxt and Vercel ecosystems:
@nuxt/*,@nuxtjs/*,nuxt,nuxt-*@vercel/*,@ai-sdk/*,aiTest plan
pnpm installresolves cleanly with v11 (lockfile already verified via--lockfile-only, 1975 entries pass supply-chain policies)pnpm dev:prepare)