Repository navigation
build: upgrade pnpm to 12.14.0 - #950
Merged
Merged
Conversation
Dependabot's updater supports pnpm 12 since dependabot-core#16169 and #16170 (announced in GitHub's changelog on 2026-10-20), so the 11.22.0 pin from #897 is no longer needed. pmOnFail: ignore keeps pnpm-lock.yaml a single YAML document. With the default, pnpm 12 prepends a boot document that GitHub's dependency graph reads as the whole lockfile (dependabot-core#15904, still open), which would silently stop alerts and security PRs. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
Coverage Report
File CoverageNo changed files found. |
Contributor
|
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.
Moves the repo from pnpm 11.22.0 to 12.14.0 and drops the pin from #897. Dependabot's updater runs pnpm 12 since dependabot/dependabot-core#16169 and dependabot/dependabot-core#16170 (merged 2026-09-15, announced in GitHub's changelog on 2026-10-20), so the reason for the pin is gone.
The one line to look at is
pmOnFail: ignoreinpnpm-workspace.yaml. With the default, pnpm 12 writespnpm-lock.yamlas two YAML documents, a boot document with pnpm's own binaries first. GitHub's dependency graph still reads only the first document (dependabot/dependabot-core#15904, open). Checked on 2026-10-20 against a public pnpm 12 repo through the GraphQLdependencyGraphManifestsAPI: the graph credits its lockfile with pnpm's 15 binaries and none of its 2016 project packages. For this repo that would mean no Dependabot alerts and no security PRs, with no error.ignoreis the only value that keeps the lockfile single-document;warnanderrorboth still write the boot document. The cost is that pnpm no longer switches itself to thepackageManagerversion, which the devcontainer (pnpmVersion) and CI (pnpm/action-setup) already handle. Remove the line once dependabot/dependabot-core#15904 closes.Known gap that stays: a security update of a transitive dependency locked on more than one major (
undiciis on 6, 7 and 8 here) fails on pnpm 12 (dependabot/dependabot-core#16434). Those bumps stay manual, asundicialready is.Validation
pnpm run allpassed on pnpm 12.14.0.pnpm install --frozen-lockfilepasses and leavespnpm-lock.yamlunchanged.🤖 Generated with Claude Code