Use cache@v4 and save-always option#40
Open
kruszczynski wants to merge 1 commit intorainforestapp:masterfrom
Open
Use cache@v4 and save-always option#40kruszczynski wants to merge 1 commit intorainforestapp:masterfrom
cache@v4 and save-always option#40kruszczynski wants to merge 1 commit intorainforestapp:masterfrom
Conversation
Use github's cache action and it's `save-always` option instead of a fork that still uses node 16.
Contributor
|
Looks like that |
Author
|
Shoot, nice catch @magni- I'll take a stab at the suggested solution from that issue. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cheers lovely people of rainforest!
TLDR
Use github's cache action and it's
save-alwaysoption instead of a fork that still uses node 16.Long story
So I noticed a Node 16 warning when running my RF suite
I checked out always-upload-cache action but it seems neglected. I started looking into Github's cache action issue linked in its README and noticed that the v4 Changelog mentions a
save-alwaysoption.While it's not documented a quick peek the code suggests it does exactly what always-upload-cache does.
I haven't tested that yet, I'm planning to test in next week on my suite.