Deprecation Notice - Upgrade to latest before February 1st 2025 #1510
Pinned
Link-
announced in
Announcements
Replies: 1 comment 6 replies
-
Is this really a deprecation? It feels like a very hard breaking change since it appears that all existing branches/tags will stop working unless upgraded. Is this harsh of a change really necessary? |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Context
The cache backend service has been rewritten from the ground up for improved performance and reliability. 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. The cache download performance will be the same. 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.
We will start rolling out the new backend service gradually as of February 1st, 2025. We will issue further guidance as we approach this deadline.
The legacy backend service will be sunset shortly after February 1st, 2025. We will not support both services at the same time. Refer to the migration guide below for further information on how to prevent disruption to your teams.
Migration guide
The new changes to the actions/cache should be seamless and fully backward compatible. You are not expected to change anything in your workflows to use the new service beyond upgrading to the latest releases.
In order to upgrade, edit your workflows to use one of these supported releases:
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 this action. If you are using any of these version (or have pinned to any of their SHAs), your workflows will break as of February 1st, 2025.
GitHub Enterprise Server
This deprecation will not impact any existing versions of GitHub Enterprise Server that are currently in use.
Beta Was this translation helpful? Give feedback.
All reactions