Skip to content

chore(deps): bump actions/setup-node from 4 to 6#16

Merged
znat merged 1 commit intomainfrom
dependabot/github_actions/actions/setup-node-6
May 2, 2026
Merged

chore(deps): bump actions/setup-node from 4 to 6#16
znat merged 1 commit intomainfrom
dependabot/github_actions/actions/setup-node-6

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 2, 2026

Bumps actions/setup-node from 4 to 6.

Release notes

Sourced from actions/setup-node's releases.

v6.0.0

What's Changed

Breaking Changes

Dependency Upgrades

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

v5.0.0

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

v4.4.0

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels May 2, 2026
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 2, 2026

Greptile Summary

Bumps actions/setup-node from v4 to v6 across all three GitHub Actions workflows (ci.yml, publish.yaml, release.yml). The explicit cache: yarn input used in all workflows remains valid in v6 — the breaking changes in v5 and v6 only affected automatic package manager detection, not explicitly configured caching.

Confidence Score: 5/5

Safe to merge — routine dependency bump with no logic changes and no breaking-change impact given explicit yarn cache config.

All three files perform an identical, minimal version bump. The v5/v6 breaking changes (automatic package-manager detection) do not apply because all workflows use the explicit cache: yarn input. No other configuration is touched.

No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/ci.yml Bumps actions/setup-node from v4 to v6; explicit cache: yarn input is preserved and continues to work in v6.
.github/workflows/publish.yaml Bumps actions/setup-node from v4 to v6 in the publish workflow; no other changes.
.github/workflows/release.yml Bumps actions/setup-node from v4 to v6 in the release workflow; no other changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[GitHub Actions Trigger] --> B[checkout]
    B --> C[setup-node v6]
    C --> D{cache yarn}
    D -->|Explicit input still supported| E[Yarn cache restored]
    E --> F[Install and Build / Test / Publish / Release]
Loading

Reviews (2): Last reviewed commit: "chore(deps): bump actions/setup-node fro..." | Re-trigger Greptile

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4...v6)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/github_actions/actions/setup-node-6 branch from 48740c0 to dfd6641 Compare May 2, 2026 12:18
@znat znat merged commit 49b2b30 into main May 2, 2026
3 checks passed
@dependabot dependabot Bot deleted the dependabot/github_actions/actions/setup-node-6 branch May 2, 2026 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant