-
Notifications
You must be signed in to change notification settings - Fork 3
chore: upgrade pnpm 9 → 11 with supply-chain protection #235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cameronapak
wants to merge
8
commits into
main
Choose a base branch
from
chore/pnpm-11-upgrade-supply-chain-protection
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
2c331e2
chore: upgrade pnpm 9 → 11 with supply-chain protection
cameronapak fcc24a0
fix: bump Node to 22 in CI, remove redundant minimumReleaseAgeExclude
cameronapak 1dc8978
Merge branch 'main' into chore/pnpm-11-upgrade-supply-chain-protection
cameronapak 54e7f03
Merge branch 'main' into chore/pnpm-11-upgrade-supply-chain-protection
camrun91 de5eb6d
Merge branch 'main' into chore/pnpm-11-upgrade-supply-chain-protection
cameronapak d8794fa
Merge main; bump pnpm 11.10.0, pin vite exact, drop swc build
cameronapak 6081568
Merge branch 'main' into chore/pnpm-11-upgrade-supply-chain-protection
cameronapak 62b088e
chore: migrate dead .npmrc settings to pnpm-workspace.yaml
cameronapak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,3 @@ | ||
| # Better configuration than shamefully-hoist | ||
| auto-install-peers=true | ||
| strict-peer-dependencies=false | ||
| public-hoist-pattern[]=*eslint* | ||
| public-hoist-pattern[]=*prettier* | ||
| public-hoist-pattern[]="@types/*" | ||
| # pnpm 11 reads ONLY auth/registry settings from .npmrc. | ||
| # All other pnpm settings live in pnpm-workspace.yaml. | ||
| # (https://pnpm.io/blog/releases/11.0) |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
engines.nodefloor of22.0.0is too low for pnpm 11. pnpm 11 relies on thenode:sqlitebuilt-in module, which was only added in Node 22.13. A developer on Node 22.0–22.12 would pass theenginesgate and then hit a crypticERR_UNKNOWN_BUILTIN_MODULE: No such built-in module: node:sqlitecrash from pnpm itself. AGENTS.md in this same PR already documents the correct minimum: "pnpm 11 requires Node >= 22.13".Prompt To Fix With AI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also not sure about this lol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My original comment was incorrect. I verified against the pnpm 11 release notes and official docs — the documented minimum is Node.js >= 22.0.0, not 22.13. While pnpm 11 does use
node:sqliteinternally, it does not require 22.13 specifically.Your
"node": ">=22.0.0"is correct. Disregard this comment.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Dustin-Kelley its funny becuase this is the exact same thing Cluade called out with a little more info
package.json:7 — engines.node is set to ">=22.0.0", but pnpm 11.1.1 (pinned via packageManager) actually requires Node >=22.13(verified against npm registry metadata). The PR's own AGENTS.md:122 edit even says so in a parenthetical added in the same commit:"Minimum version 22.0.0 required (pnpm 11 requires Node >= 22.13)" — the doc and the enforced engines field disagree with each other.A contributor on Node 22.0–22.12 passes the engines check but then hits a confusing pnpm failure. Fix: bump engines.node to">=22.13.0".
@cameronapak may be worth verifying