GitHub actions: update "cache" version for set-state deprecation #1807
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
Out GitHub actions had been pinned to [email protected], but this used the old method of set-state that GH is deprecating. Any version of cache after [email protected] will contain the fix
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.
This is ready for merging.
Feature or improvement description
An update to GitHub actions is deprecating the
save-stateandset-outputcommands. We used these indirectly through theactions/[email protected]package. The cache package was updated to not use the deprecated GH commands in the v3.2.4 release. Setting toactions/cache@3will pick the latest version.Related issue, if one exists
No issue, just annoying warnings from GH actions.
Impacted areas of the software
GitHub actions testing envionrment
Additional supporting information
From the GH actions on one of our automated tests during a PR: