Samir marin patch 1 node16 and update actions/core to latest #3
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
|
@jgiannuzzi are you still maintaining this repo? i'm not super versed with JS actions let me know if this is not the right way to go about updating these. |
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.
Currently running workflows with this action complains that node 12 will be depreciated and the
set-outputcommand is deprecated and will be disabled soon:Updating actions.yaml to ref Node 16 as suggested by warning.
ran
npm update @actions/coreto grab the latest (1.10.0) actions/core version, this update adds logic to actions/core to use the new process for setting outputs described here