This repository has been archived by the owner on Feb 25, 2021. It is now read-only.
GitHub Action: Avoid issues with set-env used by older versions of setup actions #157
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.
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
contains:
Action authors who are using the toolkit should update the @actions/core package to v1.2.6 or greater to get the updated addPath and exportVariable functions.
and
Action and workflow authors who are setting environment variables via STDOUT should update any usage of the set-env and add-path workflow commands to use the new environment files.
Which setup-node appear to have done in actions/setup-node#200 - the commits for which have been tagged v2.1.2.
And which setup-ruby appear to have done in ruby/setup-ruby#91 - the commits for which have been tagged v1.46.1.