chore(deps): update actions/cache action to v5#27
Conversation
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
| - uses: actions/checkout@v2 | ||
| - name: Cache gems | ||
| uses: actions/cache@v2 | ||
| uses: actions/cache@v5 |
There was a problem hiding this comment.
Bug: The documentation.yml workflow references actions/cache@v5, a version that does not exist. This will cause the workflow to fail when it runs.
Severity: CRITICAL | Confidence: High
🔍 Detailed Analysis
The documentation.yml workflow is configured to use actions/cache@v5. However, version v5 of this GitHub Action does not exist; the latest official version is v4. This workflow is triggered upon the publication of a new release. When it runs, it will fail because it cannot resolve the non-existent action version. This will cause the documentation deployment job to crash, preventing documentation for new releases from being published.
💡 Suggested Fix
Update the uses clause in the documentation.yml workflow to reference the latest stable version of the action, which is actions/cache@v4, instead of the non-existent actions/cache@v5.
🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: .github/workflows/documentation.yml#L13
Potential issue: The `documentation.yml` workflow is configured to use
`actions/cache@v5`. However, version `v5` of this GitHub Action does not exist; the
latest official version is `v4`. This workflow is triggered upon the publication of a
new release. When it runs, it will fail because it cannot resolve the non-existent
action version. This will cause the documentation deployment job to crash, preventing
documentation for new releases from being published.
Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 7260488
This PR contains the following updates:
v2→v5Release Notes
actions/cache (actions/cache)
v5.0.5Compare Source
What's Changed
Full Changelog: actions/cache@v5...v5.0.5
v5.0.4Compare Source
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.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
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
v4.0.2Compare Source
What's Changed
fail-on-cache-missnot working by @cdce8p in #1327Full Changelog: actions/cache@v4.0.1...v4.0.2
v4.0.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4...v4.0.1
v4.0.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v4.0.0
v4Compare Source
v3.5.0Compare Source
actions/cacheto v4.1.0Full Changelog: actions/cache@v3...v3.5.0
v3.4.3Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.2...v3.4.3
v3.4.2Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.0...v3.4.2
v3.4.1Compare Source
v3.4.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@v3.3.3...v3.4.0
v3.3.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.3
v3.3.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.2
v3.3.1Compare Source
What's Changed
Full Changelog: actions/cache@v3...v3.3.1
v3.3.0Compare Source
What's Changed
lookup-onlyoption by @cdce8p in #1041New Contributors
Full Changelog: actions/cache@v3...v3.3.0
v3.2.6Compare Source
What's Changed
Full Changelog: actions/cache@v3...v3.2.6
v3.2.5Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.5
v3.2.4Compare Source
What's Changed
set-outputcommand is deprecated by @siguikesse in #1046fail-on-cache-missoption by @cdce8p in #1036New Contributors
Full Changelog: actions/cache@v3...v3.2.4
v3.2.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.3
v3.2.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3.2.1...v3.2.2
v3.2.1Compare Source
What's Changed
Full Changelog: actions/cache@v3.2.0...v3.2.1
v3.2.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.0
v3.0.11Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.0.11
v3.0.10Compare Source
restore-keysin README.mdv3.0.9Compare Source
v3.0.8Compare Source
What's Changed
zstdnot working for windows on gnu tar in issues.SEGMENT_DOWNLOAD_TIMEOUT_MIN. Default is 60 minutes.v3.0.7Compare Source
What's Changed
v3.0.6Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.0.6
v3.0.5Compare Source
Removed error handling by consuming actions/cache 3.0 toolkit, Now cache server error handling will be done by toolkit.
v3.0.4Compare Source
In this release, we have fixed the tar creation error while trying to create it with path as
~/home folder onubuntu-latest.v3.0.3Compare Source
Fixed avoiding empty cache save when no files are available for caching. (#624)
v3.0.2Compare Source
This release adds the support for dynamic cache size cap on GHES.
v3.0.1Compare Source
v3.0.0Compare Source
This change adds a minimum runner version(node12 -> node16), which can break users using an out-of-date/fork of the runner. This would be most commonly affecting users on GHES 3.3 or before, as those runners do not support node16 actions and they can use actions from github.com via github connect or manually copying the repo to their GHES instance.
Few dependencies and cache action usage examples have also been updated.
v3Compare Source
v2.1.8: Updating actions/core to version 1.10.0Compare Source
The ::save-state and ::set-output are deprecated. The newer version of actions/core >1.10.0 uses the new syntax for save and set output. After this change, customers using actions/cache@v2 won't see deprecation warning message.
v2.1.7Compare Source
Support 10GB cache upload using the latest version
1.0.8of@actions/cachev2.1.6Compare Source
v2.1.5Compare Source
v2.1.4Compare Source
v2.1.3Compare Source
@actions/coreto v1.2.6 for CVE-2020-15228. This action was not using the affected methods.uploadChunkwhere 400-level errors were not being detected and handled correctlyv2.1.2Compare Source
v2.1.1Compare Source
@actions/cachepackage tov1.0.2which allows cache action to use posix format when taring files.v2.1.0Compare Source
http-clientwith the Azure Storage SDK for NodeJS when downloading cache content from Azure. This should help improve download performance and reliability as the SDK downloads files in 4 MB chunks, which can be parallelized and retried independentlyConfiguration
📅 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.