Modernize deprecated ::set-output to \ - #1
Open
KarloffsGhost wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
1 participant
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.
GitHub deprecated the ::set-output workflow command (github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands) in favor of writing to the $GITHUB_OUTPUT environment file. GitHub has since postponed actual removal indefinitely, so this workflow still runs fine today with only a deprecation warning — this is a forward-compatible modernization, not a repair of something currently broken.
This is a mechanically verified, byte-precise, line-for-line replacement of all 6 ::set-output call sites in this file with the equivalent $GITHUB_OUTPUT form. The transform was checked for syntax correctness, shell-context safety, runner-capability compatibility, and re-scanned afterward to confirm zero remaining deprecated call sites, then confirmed the resulting YAML still parses. No other content in the file was touched.
Opened against my own fork first.