Patch set-output
deprecation in workflows
#9543
Merged
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.
Changes
I've noticed some workflows are showing warning about
set-output
deprecation.This PR updates all workflows that are using
set-output
to use the new environment files instead.This has been done following GitHub's "GitHub Actions: Deprecating save-state and set-output commands" blog post and instructions on updating.
Testing
I've run syntax checks on the updated workflow files.
Their behavior should not change.
The
check-merge.yml
workflow should run on this PR, succeed, and the step "Check if any changesets contain minor changes" should not show any warning anymore.The
main.yml
andrelease.yml
workflows won't run on this PR. I don't know how to rigorously test them further after syntax checks.Docs
This only fixes a deprecation warning.