GHA v1-v2 of actions/cache are closing down #469
Labels
ci/cd
changes related to ci/cd
dependencies
dependency upgrade/update
github-action
related to the build-chain github action component
Starting February 1st, 2025, we are closing down v1-v2 of actions/cache (read more about it in this changelog announcement) as well as all previous versions of the @actions/cache package in actions/toolkit. Attempting to use a version of the @actions/cache package or actions/cache after the announced deprecation date will result in a workflow failure. If you are pinned to a specific version or SHA of the cache action, your workflows will also fail after February 1st.
What you need to do:
We strongly encourage you to update your workflows to begin using a supported version of actions/cache, and upgrade your actions or other products that depend on the @actions/cache package to 4.0.0 or above.
Supported versions and tags:
actions/cache:
| actions/cache@v4
actions/cache@v3
actions/[email protected]
actions/[email protected]
accessible from the UI or REST API regardless of the version used to
Starting February 1st, 2025, we are closing down v1-v2 of actions/cache (read more about it in this changelog announcement) as well as all previous versions of the @actions/cache package in actions/toolkit. Attempting to use a version of the @actions/cache package or actions/cache after the announced deprecation date will result in a workflow failure. If you are pinned to a specific version or SHA of the cache action, your workflows will also fail after February 1st.upload.
What you need to do:
We strongly encourage you to update your workflows to begin using a supported version of actions/cache, and upgrade your actions or other products that depend on the @actions/cache package to 4.0.0 or above.
Supported versions and tags:
actions/cache:
actions/cache@v4
actions/cache@v3
actions/[email protected]
actions/[email protected]
@actions/cache package in actions/toolkit: 4.0.0
Cached entries within their retention period will remain accessible from the UI or REST API regardless of the version used to upload.
The text was updated successfully, but these errors were encountered: