fix(deps): align devEngines pnpm with packageManager to 11.11.0 - #1412
Open
l2ysho wants to merge 1 commit into
Open
fix(deps): align devEngines pnpm with packageManager to 11.11.0#1412l2ysho wants to merge 1 commit into
l2ysho wants to merge 1 commit into
Conversation
pnpm ignored the 11.11.0 packageManager pin because devEngines still requested 11.8.0, so installs resolved the older version and the lockfile pinned pnpm 11.8.0. That version is covered by three high severity advisories. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
github-actions
Bot
added
the
t-tooling
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
2 participants
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.
Note
TL;DR —
devEngines.packageManagerstill asked for pnpm 11.8.0, which made pnpm ignore the 11.11.0packageManagerpin and install the old version. Bumps it to 11.11.0 and refreshes the lockfile, clearing 3 high-severity Dependabot alerts.What
package.json:devEngines.packageManager.version11.8.0 → 11.11.0pnpm-lock.yaml:packageManagerDependencies(pnpm,@pnpm/exe+ platform binaries) 11.8.0 → 11.11.0Nothing else changes — the lockfile diff contains only pnpm's own entries.
Why
packageManagerandvolta.pnpmwere already 11.11.0, butdevEngines.packageManagerlagged at 11.8.0. pnpm resolves the mismatch by discardingpackageManager:So installs used 11.8.0 and the lockfile pinned it. That is the source of the three open high-severity advisories against pnpm
>= 11.0.0, < 11.11.0(path traversal in the virtual store linker, arbitrary file write via a tarball manifestname, and env-secret exfiltration through proxy placeholder expansion).Supersedes #1398, which carried the same bump but is based on pre-Node-22 master and would revert #1343, #1390 and #1391.
Install size
No effect on the published package — the change is dev tooling metadata plus the lockfile.
Checks
lint,oxfmt --check,buildandtest:local(550 passed) all clean locally.