Use GITHUB_OUTPUT for action outputs #2

Closed

stephen wants to merge 0 commits from fix/runner13-output-file-command into main

stephen commented

2026-08-05 20:32:24 +00:00

Owner

What changed:

Updated the shared action core setOutput helper to require GITHUB_OUTPUT and write outputs through the runner file-command path instead of falling back to the deprecated ::set-output workflow command.

How I checked the output still reaches its consumer:

The changed setOutput path still appends a heredoc record named with the exact output key passed by each action implementation.
For this action, the implementation calls core.setOutput for: build-number, version-name.
Those names match the outputs declared in action.yml, so workflow consumers reading steps..outputs. continue to read the same keys after the runner parses GITHUB_OUTPUT.

What changed: - Updated the shared action core setOutput helper to require GITHUB_OUTPUT and write outputs through the runner file-command path instead of falling back to the deprecated ::set-output workflow command. How I checked the output still reaches its consumer: - The changed setOutput path still appends a heredoc record named with the exact output key passed by each action implementation. - For this action, the implementation calls core.setOutput for: build-number, version-name. - Those names match the outputs declared in action.yml, so workflow consumers reading steps.<id>.outputs.<name> continue to read the same keys after the runner parses GITHUB_OUTPUT.

stephen closed this pull request

2026-08-05 20:36:56 +00:00