Skip to content

chore(deps): update github-actions to v6#112

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-github-actions
Closed

chore(deps): update github-actions to v6#112
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-github-actions

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 18, 2026

This PR contains the following updates:

Package Type Update Change Pending
actions/checkout action major v4v6
actions/setup-node action major v4v6
pnpm/action-setup action major v4v6 v6.0.8 (+2)

Release Notes

actions/checkout (actions/checkout)

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v6

Compare Source

v5.0.1

Compare Source

What's Changed

Full Changelog: actions/checkout@v5...v5.0.1

v5.0.0

Compare Source

What's Changed
⚠️ Minimum Compatible Runner Version

v2.327.1
Release Notes

Make sure your runner is updated to this version or newer to use this release.

Full Changelog: actions/checkout@v4...v5.0.0

v5

Compare Source

v4.3.1

Compare Source

What's Changed

Full Changelog: actions/checkout@v4...v4.3.1

v4.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/checkout@v4...v4.3.0

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.7

Compare Source

v4.1.6

Compare Source

v4.1.5

Compare Source

v4.1.4

Compare Source

v4.1.3

Compare Source

v4.1.2

Compare Source

  • Fix: Disable sparse checkout whenever sparse-checkout option is not present @​dscho in #​1598

v4.1.1

Compare Source

v4.1.0

Compare Source

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

v6.4.0

Compare Source

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

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

v6

Compare Source

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

v5

Compare Source

v4.4.0

Compare Source

What's Changed
Bug fixes:
Enhancement:
Dependency update:
New Contributors

Full Changelogactions/setup-node@v4...v4.4.0

v4.3.0

Compare Source

What's Changed
Dependency updates
New Contributors

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

v4.2.0

Compare Source

What's Changed
New Contributors

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

v4.1.0

Compare Source

What's Changed
  • Resolve High Security Alerts by upgrading Dependencies by @​aparnajyothi-y in #​1132
  • Upgrade IA Publish by @​Jcambass in #​1134
  • Revise isGhes logic by @​jww3 in #​1148
  • Add architecture to cache key by @​pengx17 in #​843
    This addresses issues with caching by adding the architecture (arch) to the cache key, ensuring that cache keys are accurate to prevent conflicts.
    Note: This change may break previous cache keys as they will no longer be compatible with the new format.
New Contributors

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

v4.0.4

Compare Source

What's Changed
Documentation changes:
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.4

v4.0.3

Compare Source

What's Changed
Bug fixes:
Documentation changes:
Dependency updates:
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.3

v4.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.1

pnpm/action-setup (pnpm/action-setup)

v6.0.5

Compare Source

What's Changed
  • fix: append (not prepend) action node dir to PATH for npm bootstrap by @​zkochan in #​241

Full Changelog: pnpm/action-setup@v6.0.4...v6.0.5

v6.0.4

Compare Source

What's Changed
New Contributors

Full Changelog: pnpm/action-setup@v6.0.3...v6.0.4

v6.0.3

Compare Source

Updated pnpm to v11.0.0-rc.5

Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3

v6.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2

v6.0.1

Compare Source

Update pnpm to v11.0.0-rc.2. pnpm-lock.yaml will not be saved with two documents unless the packageManager is set via devEngines.packageManager. Related issue: #​228

v6.0.0

Compare Source

v6

Compare Source

v5.0.0

Compare Source

Updated the action to use Node.js 24.

v5

Compare Source

v4.4.0

Compare Source

Updated the action to use Node.js 24.

v4.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: pnpm/action-setup@v4.2.0...v4.3.0

v4.2.0

Compare Source

When there's a .npmrc file at the root of the repository, pnpm will be fetched from the registry that is specified in that .npmrc file #​179

v4.1.0

Compare Source

Add support for package.yaml #​156.


Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • Between 12:00 AM and 05:59 AM, on day 1 through 7 and 15 through 21 of the month, and on Monday (* 0-5 1-7,15-21 * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.


Note

Medium Risk
CI/release pipelines now depend on new major versions of actions/checkout, actions/setup-node, and pnpm/action-setup, which could change runner behavior or caching and cause workflow failures. No application/runtime code changes.

Overview
Updates the GitHub Actions workflows (pr.yaml, release.yaml) to use v6 of actions/checkout, actions/setup-node, and pnpm/action-setup (from v4).

This changes only CI/release execution dependencies; the job steps and Node version (24) remain the same.

Reviewed by Cursor Bugbot for commit 70ba2d7. Bugbot is set up for automated code reviews on this repo. Configure here.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 18, 2026

Greptile Summary

Bumps actions/checkout, pnpm/action-setup, and actions/setup-node from v4 to v6 across both CI workflow files, skipping the v5 intermediate releases.

  • All three actions jump directly to v6, which requires runner version ≥ v2.327.1 (GitHub-hosted ubuntu-24.04 runners should satisfy this automatically).
  • actions/setup-node v6.0.0 introduced a breaking change limiting automatic caching to npm only; the cache: 'pnpm' option in both workflows may now be silently no-oped or unsupported, potentially leaving pnpm dependency caching non-functional in CI.

Confidence Score: 4/5

Routine action version bumps; the workflows will continue to run but pnpm dependency caching may stop working.

The change is a straightforward dependency update and the core workflow steps remain intact. The only realistic concern is that setup-node@v6 dropped support for non-npm automatic caching, which means the cache: pnpm option may no longer function — this would slow down CI runs but would not break the build or release itself.

Both workflow files should be checked after merge to confirm pnpm cache hits are still occurring; if not, the cache: pnpm option on setup-node should be removed and caching delegated to pnpm/action-setup alone.

Important Files Changed

Filename Overview
.github/workflows/pr.yaml Updates actions/checkout, pnpm/action-setup, and actions/setup-node from v4 to v6; setup-node v6 limits automatic caching to npm, which may affect the pnpm cache configuration.
.github/workflows/release.yaml Same action version bumps as pr.yaml; carries the same potential pnpm cache concern with setup-node v6.

Comments Outside Diff (1)

  1. .github/workflows/pr.yaml, line 22-24 (link)

    P2 setup-node@v6 breaking change may affect pnpm cache

    actions/setup-node v6.0.0 introduced a breaking change: "Limit automatic caching to npm." The explicit cache: 'pnpm' setting here may now be silently ignored or unsupported. Since pnpm/action-setup@v6 manages its own caching, having both attempt to configure pnpm caching could conflict or result in no caching at all, slowing down CI. Consider removing cache: 'pnpm' from setup-node and relying solely on pnpm/action-setup for caching.

Reviews (1): Last reviewed commit: "chore(deps): update github-actions to v6" | Re-trigger Greptile

@renovate renovate Bot force-pushed the renovate/major-github-actions branch from adb6953 to 70ba2d7 Compare May 18, 2026 07:56
@designcode designcode closed this May 18, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 18, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate Bot deleted the renovate/major-github-actions branch May 18, 2026 08:06
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.

1 participant