[ci] upgrade to cache v4 #27898
Merged
[ci] upgrade to cache v4 #27898
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
tsapeta
approved these changes
Mar 27, 2024
brentvatne
approved these changes
Mar 27, 2024
kbrandwijk
deleted the
kbrandwijk/eng-11815-action-in-expoexpo-requires-upgrading-to-actioncachev4
branch
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.
Why
actions/cache@v3 runs on Node 16 which is no longer supported. Upgrading to v4 has no breaking changes and includes only running on Node 20 now, so the upgrade should be painless.
How
Replaced all instances of cache@v3 by cache@v4
Test Plan
Not sure how to test this properly. Maybe by seeing the actions on this PR branch run without the warning message? Although it seems that it doesn't pick up the change.
Checklist
npx expo prebuild& EAS Build (eg: updated a module plugin).