ci(deps): update actions/cache to v4 #787
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
1 task
jennifer-shehane
approved these changes
Feb 2, 2024
|
🎉 This PR is included in version 2.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v4for compatibility withnode20.Issue
The following workflows output a deprecation warning when run on GitHub:
Deprecation warning:
actions/upload-artifact@v3. This PR is for the deprecation issue withactions/cache@v3Changes
actions/cache from v3 to v4
All usage of actions/cache is migrated from
v3tov4.actions/cache@v3runs undernode16actions/cache@v4runs undernode20Verification
Manually run each GitHub Actions workflow and check for success. The following workflows record to Cypress Cloud and need special handling to test in a fork:
These fail when tested unchanged in a fork with the error message:
To tests these workflows in a fork, check out the branch of this PR and modify the
projectIdcypress-example-kitchensink/cypress.config.js
Line 2 in 277e055
to use a personal
projectIdand create a GitHub Actions secretDASHBOARDRECORDKEYwith the corresponding Cypress Cloud Record Key available from the Cypress Cloud Project settings UI.