chore(deps): update actions/setup-node action to v6#27
Conversation
renovate
Bot
force-pushed
the
renovate/actions-setup-node-6.x
branch
2 times, most recently
from
cdfbcdc to
68d7299
Compare
renovate
Bot
force-pushed
the
renovate/actions-setup-node-6.x
branch
from
68d7299 to
82af44e
Compare
renovate
Bot
force-pushed
the
renovate/actions-setup-node-6.x
branch
from
82af44e to
07fcddd
Compare
![doubleword-code[bot]](https://avatars.githubusercontent.com/in/3610877?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary
This PR updates the actions/setup-node GitHub Action from v4 to v6 in both CI and publish workflows. This is a routine dependency maintenance update.
Verdict: Approved — Safe to merge. No code changes required.
Research notes
I reviewed the official actions/setup-node repository for breaking changes between v4→v6:
Breaking changes in v6:
- Automatic caching enabled for npm projects when
packageManagerordevEngines.packageManagerinpackage.jsonis set tonpm always-authinput removed (deprecated)
Breaking changes in v5:
- Caching enabled by default with package manager detection
- Action runtime upgraded from node20 to node24
Impact on this repo: Neither workflow uses the always-auth input (no migration needed). The workflows don't specify cache: explicitly, so behavior depends on whether typescript/package.json declares a packageManager field — if it does and it's npm, caching becomes automatic (a benefit); otherwise, behavior is unchanged. The action's internal runtime upgrade (node20→node24) doesn't affect the node-version: "22" that the workflow explicitly requests.
Suggested next steps
- Merge this PR as-is — no changes needed.
- (Optional follow-up) Consider explicitly adding
cache: 'npm'to the TypeScript workflow if you want deterministic caching behavior regardless ofpackage.jsoncontents, or add apackageManagerfield totypescript/package.jsonto leverage the new automatic caching.
General findings
None. This is a straightforward, low-risk dependency bump with no regressions identified.
renovate
Bot
force-pushed
the
renovate/actions-setup-node-6.x
branch
from
07fcddd to
1e89517
Compare
There was a problem hiding this comment.
Summary
This PR updates the actions/setup-node GitHub Action from v4 to v6 in two workflow files (.github/workflows/ci.yml and .github/workflows/publish.yml). This is a routine dependency upgrade that brings security patches, bug fixes, and aligns with current best practices.
Verdict: Approved — The upgrade is safe and recommended. No breaking changes affect this repository's workflows.
Research notes
I reviewed the v6.0.0 release notes and main documentation:
Breaking changes in v6
- Caching behavior: Automatic caching is now limited to npm projects where
devEngines.packageManagerorpackageManagerfield inpackage.jsonis set tonpm. Other package managers (Yarn, pnpm) require explicitcache:configuration. always-authinput removed: Deprecated and no longer supported.
Breaking changes in v5 (also relevant since upgrading from v4 → v6)
- Enabled caching by default with package manager detection if no
cacheinput is provided. - Upgraded action runtime from node20 to node24 (requires runner v2.327.1+).
Impact assessment for this repository
The typescript/package.json does not include a packageManager or devEngines.packageManager field. Since the workflows also don't explicitly specify cache: 'npm', the new automatic caching will not be triggered. The current behavior (no caching) remains unchanged after this upgrade.
If caching is desired for faster CI builds, consider adding cache: 'npm' to the setup-node steps in a follow-up PR.
Suggested next steps
- Merge this PR — The upgrade is safe and has no adverse impact on existing functionality.
- (Optional follow-up) Consider whether npm dependency caching would benefit CI performance. If so, add
cache: 'npm'to both workflow files:- uses: actions/setup-node@v6 with: node-version: "22" cache: 'npm' # Add this line
General findings
None. The change is minimal, well-scoped, and follows standard dependency update practices.
renovate
Bot
force-pushed
the
renovate/actions-setup-node-6.x
branch
from
1e89517 to
48235d6
Compare
This PR contains the following updates:
v4→v6Release Notes
actions/setup-node (actions/setup-node)
v6.4.0Compare Source
What's Changed
Dependency updates:
New Contributors
Full Changelog: actions/setup-node@v6...v6.4.0
v6.3.0Compare Source
What's Changed
Enhancements:
devEnginesfield by @susnux in #1283Dependency updates:
Bug fixes:
New Contributors
Full Changelog: actions/setup-node@v6...v6.3.0
v6.2.0Compare Source
What's Changed
Documentation
Dependency updates:
New Contributors
Full Changelog: actions/setup-node@v6...v6.2.0
v6.1.0Compare Source
What's Changed
Enhancement:
Dependency updates:
Documentation update:
Full Changelog: actions/setup-node@v6...v6.1.0
v6.0.0Compare Source
What's Changed
Breaking Changes
Dependency Upgrades
Full Changelog: actions/setup-node@v5...v6.0.0
v6Compare Source
v5.0.0Compare Source
What's Changed
Breaking Changes
This update, introduces automatic caching when a valid
packageManagerfield is present in yourpackage.json. This aims to improve workflow performance and make dependency management more seamless.To disable this automatic caching, set
package-manager-cache: falseMake sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes
Dependency Upgrades
New Contributors
Full Changelog: actions/setup-node@v4...v5.0.0
v5Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.