Emit release-notes via $GITHUB_OUTPUT instead of disabled set-output#23
Merged
Conversation
…tput GitHub disabled the legacy ::set-output workflow command in recent runner versions, so the action's output was silently dropped — every consumer (vendor-portal, sdk, embedded-cluster, kots, ... release notes) started generating empty notes and opening no PR, while the job still exited 0. Write the multi-line result to the step output via the environment file with a random heredoc delimiter. Drops the %25/%0A/%0D escaping, which was only needed for set-output's encoding (and mangled literal % signs).
divolgin
approved these changes
Jun 26, 2026
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
2 participants
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.
What this PR does
Fixes the action so it stops returning empty output. It now writes the generated release notes to the step output via the
$GITHUB_OUTPUTenvironment file instead of the legacy::set-outputworkflow command.Why
GitHub disabled
::set-outputin recent runner versions (it now only prints a deprecation warning and ignores the command). Because this action returned its result withecho "::set-output name=release-notes::...", therelease-notesoutput silently became empty. Every workflow that consumes this action — vendor-portal, replicated-sdk, embedded-cluster, kots, etc. release notes — then generated nothing and opened no PR, while the job still exited 0 (so it looked successful).This is why Vendor Platform release notes have had no PRs since ~June 8.
The change
release-notesvia$GITHUB_OUTPUTusing a random heredoc delimiter (multi-line safe).%25/%0A/%0Descaping — that was only required forset-output's encoding, and it also mangled literal%signs in release notes.Workflows pin this action at
@mainand it is built from source each run, so consumers recover automatically once this merges — no changes needed in replicated-docs or any product repo.Verification
Simulated the output block with multi-line content containing
%,<>, backticks, and blank lines; the value written to$GITHUB_OUTPUTround-trips and parses back identically.Note: this fixes generation going forward. The ~2.5 weeks of already-missed notes (June 8 → now) will need a separate catch-up run over that version range.