Update to node16 and actions/core to latest #1
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
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.
First attempted to contribute directly to the open source project, but it seems the repo is not still being actively maintained, so forked the project and made the updates directly here. Project is very simple so it won't require a lot of maintenance other than version updates every few months as we doing here.
We are currently running workflows with this action that complain that node 12 will be depreciated and the
set-outputcommand is deprecated and will be disabled soon, to fix we are: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