Skip to content

chore(deps): update actions/cache action to v5 - autoclosed#199

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/actions-cache-5.x
Closed

chore(deps): update actions/cache action to v5 - autoclosed#199
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/actions-cache-5.x

Conversation

@renovate

@renovate renovate Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
actions/cache action major v4.3.0v5.0.5
actions/cache action major v4v5

Release Notes

actions/cache (actions/cache)

v5.0.5

Compare Source

What's Changed

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

v5.0.4

Compare Source

v5.0.3

Compare Source

What's Changed

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

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

v5

Compare Source


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

@renovate
renovate Bot force-pushed the renovate/actions-cache-5.x branch from 9e9661e to b81bb7a Compare May 20, 2026 02:00
@renovate renovate Bot changed the title chore(deps): update actions/cache action to v5 chore(deps): update actions/cache action to v5 - autoclosed Jul 25, 2026
@renovate renovate Bot closed this Jul 25, 2026
@renovate
renovate Bot deleted the renovate/actions-cache-5.x branch July 25, 2026 20:09
GSTJ added a commit that referenced this pull request Jul 25, 2026
Renovate had these as #200 and #199 and then autoclosed both without
merging, so main is still on v4 everywhere. Same diff, reapplied by
hand.

Both majors are just the Node 24 runtime move, which is the thing every
run has been warning about ("Node.js 20 actions are deprecated... forced
to Node.js 24 by default starting June 2nd, 2026"). No input or
behaviour changes on our side.

Only the version tags move. Worth watching the first e2e run since it's
the heaviest cache user, but restore/save keys are untouched.
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