Require GITHUB_OUTPUT for runner 13 #20

Merged
stephen merged 1 commit from runner13-workflow-compat into main 2026-08-04 21:27:25 +00:00
Owner

Forgejo Runner 13 removes the legacy set-output workflow command. This action already uses the GITHUB_OUTPUT file-command path on supported runners; make that path mandatory so outputs cannot silently fall back to a removed command.

What changed

  • Removed the set-output fallback from the local core shim.
  • Kept the existing GITHUB_OUTPUT heredoc writer for multiline-safe outputs.

Testing

  • npm test verifies downloaded artifact paths and metadata outputs round-trip through the action flow.
  • npm run check
Forgejo Runner 13 removes the legacy set-output workflow command. This action already uses the GITHUB_OUTPUT file-command path on supported runners; make that path mandatory so outputs cannot silently fall back to a removed command. **What changed** - Removed the set-output fallback from the local core shim. - Kept the existing GITHUB_OUTPUT heredoc writer for multiline-safe outputs. **Testing** - `npm test` verifies downloaded artifact paths and metadata outputs round-trip through the action flow. - `npm run check`
Require GITHUB_OUTPUT for action outputs
All checks were successful
test / e2e (pull_request) Successful in 4s
ci / test (pull_request) Successful in 26s
test / unit (pull_request) Successful in 28s
6a447671e9
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rasterstate/download-artifact-action!20
No description provided.