build(deps): bump pnpm/setup from 2 to 3 in /.github/actions/setup-workspace - #830
Merged
ScriptedAlchemy merged 5 commits intoSep 25, 2026
Conversation
Bumps [pnpm/setup](https://github.com/pnpm/setup) from 2 to 3. - [Release notes](https://github.com/pnpm/setup/releases) - [Commits](pnpm/setup@v2...v3) --- updated-dependencies: - dependency-name: pnpm/setup dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
commit: |
dependabot
Bot
deleted the
dependabot/github_actions/dot-github/actions/setup-workspace/pnpm/setup-3
branch
September 25, 2026 00:57
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.
Bumps pnpm/setup from 2 to 3.
Release notes
Sourced from pnpm/setup's releases.
Commits
fbda4c8docs(README): update versionc868a7dfix: require-lockfile no longer accepts a lockfile pnpm will not use (#60)463911bfix: avoid deprecated shell spawning for pnpm commands (#52)6598286docs: add private registry authentication recipes (#61)c5b2e24feat!: automatically detect Node.js version files (#49)f37addefix!: include runid in cache key, restore freshest lockfile match (#43)703c526chore: update dependencies (#42)e02cd34ci: update dependencies with pnpm/update instead of Dependabot (#41)0080ecafeat: add arequire-lockfileinput (#23)3327d57feat: addworking-directory, deprecatingpackage-json-file(#27)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Root verification verdict: PASS+NOTES at
bc826dad3cBase
b0b131bbf7, headbc826dad3c.mainhas since moved to96b2519513(#826). Both PRs editdocs/local-ci.md, but on different lines.git merge-treemerges cleanly onto96b2519513, and the merged diff has the same stable patch-id (f3e22927df) as the PR diff. The verdict pins that patch-id.The real surface of this change is CI itself, so the lanes read the PR's own CI runs against the latest green
mainrun (35403567867, still onpnpm/setup@v2).mainjob logspnpm/setup@v3(fbda4c85fc2e). Node matched the requested version on every leg. That is 22.19.0 on all host and gate jobs, 24.21.0 on the Node 24 legs, and 26.10.0 on the Node 26 leg. pnpm stayed 11.23.0. The retry step never ran.pnpm/setup@v3'saction.ymlexactly. v3's Node version-file auto-detection applies only when no version is given. This action always passesruntime, so the matrix is not collapsed. The logs confirm it.mainmain. Every PR job restored the v2-era store through the new restore prefix, so the first run after the bump is a cache hit.Note, not blocking:
mainpush and each PR run writes a similar batch, so LRU eviction will churn constantly. Restores still hit through the prefix, so the likely cost is storage churn and occasional cold installs, not failures. That cost is a prediction from these numbers, not yet observed. A follow-up could save from one job per OS, or accept the churn.CI at this head is green (
mergeStateStatusCLEAN).Maintainer notes
pnpm/setup v3 breaking changes checked against
.github/actions/setup-workspace:runtime: node@<version>, which v3 ranks above version files.cache,install,runtime) are unchanged, and no workflow readssteps.setup.outputs.*orcache-hit. The retry onsteps.setup.outcomestill works.docs/local-ci.mdto v3, and added v3'snode-version-fileinput to the listed inputs. The 2026-09-04 incident lines stay v2 because they are history.CI on bc826da was fully green. In the
Verify (fast, Node 26)log,pnpm/setup@v3ran withruntime: node@26and installed node@26. The store restored from a restore-key, and the post step saved a new per-run cache in about 5 s. Later heads only merge main (#825, #826, #817). CI-only change, so no changeset.Independent review (change-risk-reviewer, GPT-5.6 Sol Max) found no blockers and one should-fix: v3 saves a new store cache (about 195 MB) from every setup invocation. The repo was at 7.4 GB of the 10 GB cache quota. Accepted, with follow-up: GitHub evicts least-recently-accessed entries first, so the caches every run restores survive. Watch cache usage after merge, and switch fan-out jobs to restore-only if eviction starts to hurt.