GitHub Community
Deprecation Notice (reminder): v1 - v2 of Actions cache storage and packages 📣 #148746
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
-
We would like to inform everyone of the upcoming deprecation of v1-v2 of actions/cache. 📣
This deprecation will not impact any existing versions of GitHub Enterprise Server that are currently in use.
Starting February 1st, 2025, Actions’ cache storage will move to a new architecture, resulting in the deprecation of v1-v2 of actions/cache as well as the deprecation of all previous versions of the @actions/cache package in actions/toolkit.
In latest versions actions/cache, we introduced a more consistent API contract with the cache backend service. The new service will decrease the cache upload duration by up to ~80% when using GitHub Hosted Runners. If you’re using self-hosted runners the upload duration is expected to improve, or in the worst-case stay the same.
Cache upload/download performance depends on your network topology, hardware and geographical region used for hosting among other factors.
What This Means for You
Please review and update your workflows to use the latest version of actions/cache and references to actions/cache as soon as possible.
In order to upgrade actions/cache, edit your workflows to use one of these supported releases:
In order to upgrade actions/cache_packages, simply bump up the version of
@actions/cachein yourpackage.jsonto4.0.0(or above). We will be releasing bug fixes and improvements throughout the period leading to February 1st, 2025. Check out our example of a samplepackage.jsonfor your reference.If you are caching or have forked these actions, please make sure you update your caches or your forks!
The following is the list of all the deprecated versions of these actions. If you are using any of these versions (or have pinned to any of their SHAs), your workflows will break as of February 1st, 2025.
The deprecated versions:
actions/cache 👈
actions/cache_package 👈
If you’re a maintainer of solutions that depend on @actions/cache please upgrade the @actions/cache package to
4.0.0or higher and release new versions of your solutions as soon as possible.If you are a maintainer of any
setup-*action, please comment on this discussion and we will look into enabling the new service for you on a test repository, so that you can test the change before it's rolled out globally.Updated documentation and support resources are available to assist with the upgrade. 🤚
Beta Was this translation helpful? Give feedback.
All reactions