chore: upgrade pnpm to v11 and add minimumReleaseAge#347
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📝 WalkthroughWalkthroughpnpm is upgraded from 10.33.2 to 11.1.3. Configuration settings are consolidated: .npmrc entries and root package.json overrides are removed, then centralized in pnpm-workspace.yaml. Build dependency controls transition from ignoredBuiltDependencies/onlyBuiltDependencies lists to a new allowBuilds policy map with explicit per-dependency build toggles. Changespnpm upgrade and configuration consolidation
🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Contributor
|
Thank you for following the naming conventions! 🙏 |
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
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.3onlyBuiltDependencies+ignoredBuiltDependencies→ unifiedallowBuildsmap (required in v11)overridesfrompackage.json→pnpm-workspace.yaml(thepnpmfield inpackage.jsonis no longer recognized in v11)shamefullyHoistandstrictPeerDependenciesfrom.npmrc→pnpm-workspace.yaml(in v11,.npmrconly holds auth/registry).npmrc(now empty)CI already runs on Node 22 and
pnpm/action-setup@v6, which readpackageManagerfrompackage.json— no workflow changes needed.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)pnpm dev:prepareandpnpm buildSummary by CodeRabbit