Skip to content

chore(deps): update actions/setup-node action to v6#609

Open
renovate-bot-cbcoutinho[bot] wants to merge 1 commit intomasterfrom
renovate/actions-setup-node-6.x
Open

chore(deps): update actions/setup-node action to v6#609
renovate-bot-cbcoutinho[bot] wants to merge 1 commit intomasterfrom
renovate/actions-setup-node-6.x

Conversation

@renovate-bot-cbcoutinho
Copy link
Copy Markdown
Contributor

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho bot commented Mar 3, 2026

This PR contains the following updates:

Package Type Update Change
actions/setup-node action major v4.4.0v6.3.0

Release Notes

actions/setup-node (actions/setup-node)

v6.3.0

Compare Source

What's Changed
Enhancements:

When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.

Dependency updates:
Bug fixes:
New Contributors

Full Changelog: actions/setup-node@v6...v6.3.0

v6.2.0

Compare Source

What's Changed
Documentation
Dependency updates:
New Contributors

Full Changelog: actions/setup-node@v6...v6.2.0

v6.1.0

Compare Source

What's Changed
Enhancement:
Dependency updates:
Documentation update:

Full Changelog: actions/setup-node@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Breaking Changes

Dependency Upgrades

Full Changelog: actions/setup-node@v5...v6.0.0

v5.0.0

Compare Source

What's Changed
Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless.
To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make 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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@claude
Copy link
Copy Markdown

claude bot commented Mar 3, 2026

PR Review: chore(deps): update actions/setup-node action to v6

This is a clean, straightforward dependency update from Renovate Bot bumping actions/setup-node from v4.4.0v6.2.0.

What changed (1 line in .github/workflows/test.yml):

  • Pinned SHA updated from 49933ea56044e13b
  • Version comment updated from v4.4.0v6.2.0

Breaking changes between v4 and v6 to consider:

  • v5.0.0: Introduced automatic caching when a packageManager field is present in package.json, and upgraded the action to use node24 (requires runner v2.327.1+)
  • v6.0.0: Limited automatic caching to npm only (removed support for other package managers via auto-detection)

Assessment: None of the breaking changes apply here because:

  1. The workflow only uses node-version: 22 — no caching options are configured, so the auto-caching behavior change in v5/v6 is irrelevant
  2. GitHub-hosted runners are already at a version supporting node24
  3. The SHA pinning practice is correctly maintained — good security hygiene

No issues found. This update is safe to merge.

@renovate-bot-cbcoutinho renovate-bot-cbcoutinho bot force-pushed the renovate/actions-setup-node-6.x branch from 2346cd8 to ede6758 Compare March 4, 2026 05:20
@claude
Copy link
Copy Markdown

claude bot commented Mar 4, 2026

PR Review: chore(deps): update actions/setup-node v4.4.0 → v6.3.0

This is a routine Renovate dependency update for the actions/setup-node action, jumping two major versions (v4 → v6, skipping v5).

Summary of Notable Breaking Changes

v5.0.0

  • Action now runs on Node 24 (requires GitHub Actions runner ≥ v2.327.1)
  • Introduced automatic caching when a packageManager field is present in package.json

v6.0.0

  • Automatic caching is now limited to npm only — other package managers (yarn, pnpm) no longer get automatic cache behavior

Assessment

The changes look good for this use case:

  • Scope is limited: The step only runs for non-single-user modes (if: matrix.mode != 'single-user') to build the Astrolabe frontend app using npm ci + npm run build.
  • npm-only caching restriction (v6) is a non-issue: This workflow uses npm, so the breaking caching change in v6 doesn't apply.
  • node-version: 24 is unchanged and compatible with v6.
  • Commit SHA pinning is maintained (53b83947...), which is the correct security practice for this repo.
  • No cache or package-manager-cache inputs are set, so the automatic caching change in v5 won't unexpectedly alter behavior unless package.json in third_party/astrolabe has a packageManager field.

Minor Observation

Worth a quick sanity check: if third_party/astrolabe/package.json contains a packageManager field (e.g., "packageManager": "npm@..."), v5+ will now auto-cache npm dependencies in the Build Astrolabe app step. This is generally desirable (speeds up CI) but worth being aware of as a behavioral change. If unwanted, add package-manager-cache: false under with:.

Verdict

✅ Safe to merge. Low-risk dependency bump with no functional impact on the tested workflows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants