Skip to content

Update GitHub Actions actions/cache (major) - #75

Merged
thardeck merged 1 commit into
masterfrom
renovate/major-github-actions
Nov 16, 2026
Merged

thardeck merged 1 commit into
masterfrom
renovate/major-github-actions

Conversation

@renovate-rancher

@renovate-rancher renovate-rancher Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
actions/cache action major v4.3.0 → v6.1.0
actions/checkout action major v6.1.0 → v7.0.1
actions/checkout action major v4.4.0 → v7.0.1
fossas/fossa-action action major v1.9.0 → v2.0.0

Release Notes

actions/cache

v6.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v6.0.0

v5.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.1.0

v5.0.5

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

v5.0.4

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v5...v5.0.4

v5.0.3

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.3

v5.0.2: v.5.0.2

Compare Source

v5.0.2
What's Changed

When creating cache entries, 429s returned from the cache service will not be retried.

v5.0.1

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


v5.0.1
What's Changed
v5.0.0
What's Changed

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

v5.0.0

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


What's Changed

Full Changelog: actions/cache@v4.3.0...v5.0.0

actions/checkout

v7.0.1

Compare Source

v7.0.0

Compare Source

  • Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
  • Various dependency updates
fossas/fossa-action

v2.0.0

Compare Source

Breaking change: Node 24 runtime

This action now runs on the Node 24 GitHub Actions runtime (previously Node 20), via #​277.

  • GitHub-hosted runners: no action needed.
  • Self-hosted runners: you must be on a runner version that bundles the Node 24 runtime. Update your runner if you pin fossas/fossa-action@v2.

The @v1 line is unchanged and stays on Node 20, so existing @v1 users are not affected until they opt into @v2. #​277 is the only change that touches the action's runtime code (dist/) — everything else below is CI or dev-tooling only.

Everything in v1.9.0 → v2.0.0

Action runtime

  • Upgrade to Node.js 24 and Yarn 4 (Corepack, packageManager: yarn@4.13.0, engines.node >= 24.0.0) — #​277

CI / repo tooling (no effect on consumers)

  • Fix the repo's fossa test --diff CI step to work with push events (first push to a new branch falls back to diffing the default branch) — #​278
  • Make dependabot ignore major-version bumps of @types/node — #​291

Dev-dependency bumps (no effect on consumers)

Full changelog: fossas/fossa-action@v1.9.0...v2.0.0


Configuration

📅 Schedule: (UTC)

  • 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 these updates again.


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

This PR has been generated by Mend Renovate CLI.

@renovate-rancher
renovate-rancher Bot force-pushed the renovate/major-github-actions branch from ec4db79 to b490d6e Compare November 4, 2026 06:39
@thardeck
thardeck merged commit 53f3c7a into master Nov 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant