Skip to content
This repository was archived by the owner on Jan 16, 2025. It is now read-only.

Conversation

@JoelMarcey
Copy link
Contributor

v2 of cache is going to stop working.

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]
@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.

v2 of `cache` is going to stop working. 

```
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]
@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.
```
@netlify
Copy link

netlify bot commented Dec 10, 2024

Deploy Preview for suspicious-volhard-46e848 ready!

Name Link
🔨 Latest commit a8ae1fc
🔍 Latest deploy log https://app.netlify.com/sites/suspicious-volhard-46e848/deploys/6758a9d7d33af100086fa432
😎 Deploy Preview https://deploy-preview-604--suspicious-volhard-46e848.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@Turbo87
Copy link
Member

Turbo87 commented Dec 10, 2024

should we consider setting up https://github.com/renovatebot/renovate, which would automate these kinds of updates? OTOH let's hope by Feb 2025 we will have shipped the new website and won't use this repo anymore... :D

@JoelMarcey
Copy link
Contributor Author

Oh LOL - ugh. That's what I get for trying to do something technical again.

@Turbo87 Turbo87 merged commit 87c9aa7 into main Dec 11, 2024
6 checks passed
@Turbo87 Turbo87 deleted the update-cache-version branch December 11, 2024 09:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants