{{ message }}
Repository navigation
Commit 23c9f40
committed
ci(deps): bump pnpm/action-setup from 4 to 6
Two majors. v5.0.0 is only the Node 20 to Node 24 runtime move — it is the same
commit as v4.4.0 with one line changed in action.yml. v6.0.0 is the substantive
one: the bundled 9MB pnpm binary is gone, replaced by an `npm ci` bootstrap
against a committed lockfile followed by `pnpm self-update` to the requested
version, and pnpm v11 is supported.
The v6 resolution change does not affect this step. docs/package.json declares
neither `packageManager` nor `devEngines`, and the step passes `version: 10`
explicitly, which v6 still honours as the highest-priority source. The
lockfile-format hazard — `devEngines` outranking `packageManager` and causing
pnpm v11 to write a second YAML document into pnpm-lock.yaml — needs
`devEngines` to be present, and it is not.
Pinned to the `@v6` float, which resolves to v6.0.9; several intermediate
v6.0.x releases were broken and the float has since moved past them. The
`run_install: false` input is unchanged in v6. Note that v6 bootstraps through
npm, so the runner must have npm available — GitHub-hosted images do.
Releases:
https://github.com/pnpm/action-setup/releases/tag/v5.0.0
https://github.com/pnpm/action-setup/releases/tag/v6.0.0
https://github.com/pnpm/action-setup/releases/tag/v6.0.91 parent e21d82e commit 23c9f40
1 file changed
Lines changed: 1 addition & 1 deletion
0 commit comments