You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
renovate/actions-cache-6.xhttps-quantumblockchainai-atlassian-net/ai-auto-train-eip-review-bot:renovate/actions-cache-6.xCopy head branch name to clipboard
renovate/actions-cache-6.xhttps-quantumblockchainai-atlassian-net/ai-auto-train-eip-review-bot:renovate/actions-cache-6.xCopy head branch name to clipboard
Update to use @actions/cache 4.0.3 package & prepare for new release by @salmanmkc in #1577 (SAS tokens for cache entries are now masked in debug logs)
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).
If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Summary: Updates the GitHub Actions workflows to use actions/cache v6 (pinned by commit SHA) for the node_modules cache step. Why: Keeps CI/build caching on the latest major version of the action (includes upstream dependency/runtime updates such as the ESM migration).
This PR updates the actions/cache GitHub Action to v6.0.0 across both workflow files.
Bumped actions/cache from v4.0.2 to v6.0.0 in .github/workflows/build.yml
Bumped actions/cache from v4.0.2 to v6.0.0 in .github/workflows/ci.yml
Updated pinned commit hash from 0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 to 2c8a9bd7457de244a408f35966fab2fb45fda9c8 in both files
Confidence Score: 5/5 - Safe to Merge
Safe to merge — this PR performs a straightforward dependency bump of actions/cache from v4.0.2 to v6.0.0 across both .github/workflows/build.yml and .github/workflows/ci.yml, including the corresponding pinned commit hash update from 0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 to 2c8a9bd7457de244a408f35966fab2fb45fda9c8. The change is limited entirely to CI infrastructure with no impact on application logic, runtime behavior, or security posture. No review comments were generated and no pre-existing unresolved concerns apply to this change.
Key Findings:
The pinned commit hash in both workflow files was updated alongside the version tag, maintaining the security best practice of hash-pinning GitHub Actions to prevent supply chain attacks.
The version jump from v4.0.2 to v6.0.0 is a major version bump, but actions/cache is a well-maintained official GitHub Action where v6 is the current stable release — this is a routine maintenance update with no known breaking changes for standard cache usage.
Both affected files (.github/workflows/build.yml and .github/workflows/ci.yml) were reviewed and the changes are consistent and correctly applied across both locations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
This PR contains the following updates:
v4.0.2→v6.1.0Release Notes
actions/cache (actions/cache)
v6.1.0Compare Source
What's Changed
Full Changelog: actions/cache@v6...v6.1.0
v6.0.0Compare Source
What's Changed
Full Changelog: actions/cache@v5...v6.0.0
v6Compare Source
v5.1.0Compare Source
What's Changed
Full Changelog: actions/cache@v5...v5.1.0
v5.0.5Compare Source
What's Changed
Full Changelog: actions/cache@v5...v5.0.5
v5.0.4Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v5...v5.0.4
v5.0.3Compare Source
What's Changed
@actions/cacheto v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)@actions/coreto v2.0.3Full Changelog: actions/cache@v5...v5.0.3
v5.0.2: v.5.0.2Compare Source
v5.0.2
What's Changed
When creating cache entries, 429s returned from the cache service will not be retried.
v5.0.1Compare Source
v5.0.1
What's Changed
v5.0.0
What's Changed
Full Changelog: actions/cache@v5...v5.0.1
v5.0.0Compare Source
What's Changed
Full Changelog: actions/cache@v4.3.0...v5.0.0
v5Compare Source
v4.3.0Compare Source
What's Changed
v4.3.0release by @Link- in #1655New Contributors
Full Changelog: actions/cache@v4...v4.3.0
v4.2.4Compare Source
What's Changed
@actions/cacheto4.0.5and move@protobuf-ts/pluginto dev depdencies by @Link- in #16344.2.4by @Link- in #1636New Contributors
Full Changelog: actions/cache@v4...v4.2.4
v4.2.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.2.2...v4.2.3
v4.2.2Compare Source
What's Changed
Full Changelog: actions/cache@v4.2.1...v4.2.2
v4.2.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.2.0...v4.2.1
v4.2.0Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4orv3as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0orv3.4.0If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.11.1.30.38.3Full Changelog: actions/cache@v4.1.2...v4.2.0
v4.1.2Compare Source
What's Changed
isGheslogic by @jww3 in #14744.1.2release by @Link- in #1477New Contributors
Full Changelog: actions/cache@v4.1.1...v4.1.2
v4.1.1Compare Source
What's Changed
cache-hitoutput by @joshmgross in #1467Full Changelog: actions/cache@v4.1.0...v4.1.1
v4.1.0Compare Source
What's Changed
save-alwaysinput by @joshmgross in #1452New Contributors
Full Changelog: actions/cache@v4.0.2...v4.1.0
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.