Switch workflows from set-output to $GITHUB_OUTPUT #3696
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.
Motivation
Originally, the documented way to pass info from one GitHub workflow step to the next was to print this to stdout:
We used this in several places in CKAN's workflows (mainly dealing with the calculation of the version strings).
Recently GitHub decided they didn't like that anymore and added a warning message for it:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
The replacement is to append
param_name=param_value
lines to the file specified by$GITHUB_OUTPUT
:https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter
We have until June 2023 to migrate.
Noted thanks to KSP-CKAN/KSPMMCfgParser#16.
Changes
Now the prescribed migration is done for the CKAN repo.
I'll self-review this.