chore: remove workflow command set-output #1631

Merged
mfenniak merged 2 commits from aahlenst/runner:remove-set-output into main 2026-07-18 02:01:31 +00:00
Member

The workflow command set-output allows defining output variables. Unfortunately, it is difficult to use securely. Therefore, it is removed from Forgejo Runner. If workflows still use set-output, a warning will be printed. Workflows that want to set output variables can do so by writing to $FORGEJO_OUTPUT.

Instead of:

- run: |
    echo "::set-output name=MY_VARIABLE::value"

Use:

- run: |
    echo "MY_VARIABLE=value" >> "$FORGEJO_OUTPUT"

See #1455.

  • other
    • PR: chore: remove workflow command set-output
The workflow command `set-output` allows defining output variables. Unfortunately, it is difficult to use securely. Therefore, it is removed from Forgejo Runner. If workflows still use `set-output`, a warning will be printed. Workflows that want to set output variables can do so by writing to `$FORGEJO_OUTPUT`. Instead of: ```yaml - run: | echo "::set-output name=MY_VARIABLE::value" ``` Use: ```yaml - run: | echo "MY_VARIABLE=value" >> "$FORGEJO_OUTPUT" ``` See https://code.forgejo.org/forgejo/runner/issues/1455. <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/forgejo/runner--> - other - [PR](https://code.forgejo.org/forgejo/runner/pulls/1631): <!--number 1631 --><!--line 0 --><!--description Y2hvcmU6IHJlbW92ZSB3b3JrZmxvdyBjb21tYW5kIHNldC1vdXRwdXQ=-->chore: remove workflow command set-output<!--description--> <!--end release-notes-assistant-->
chore: remove workflow command set-output
All checks were successful
cascade / debug (pull_request_target) Has been skipped
test-multi-platform / Build Forgejo Runner (pull_request) Has been skipped
test-multi-platform / Build unsupported platforms (pull_request) Has been skipped
test-multi-platform / runner exec tests (pull_request) Has been skipped
test-multi-platform / Run integration tests with Docker (docker-latest) (pull_request) Has been skipped
test-multi-platform / Run integration tests with Docker (docker-stable) (pull_request) Has been skipped
test-multi-platform / Run integration tests with Podman (pull_request) Has been skipped
test-multi-platform / validate mocks (pull_request) Has been skipped
test-multi-platform / validate pre-commit-hooks file (pull_request) Has been skipped
checks / validate mocks (pull_request) Successful in 38s
checks / Build Forgejo Runner (pull_request) Successful in 45s
checks / validate pre-commit-hooks file (pull_request) Successful in 46s
checks / runner exec tests (pull_request) Successful in 43s
checks / Build unsupported platforms (pull_request) Successful in 1m16s
checks / Run integration tests with Docker (docker-latest) (pull_request) Successful in 15m1s
checks / Run integration tests with Podman (pull_request) Successful in 18m18s
checks / Run integration tests with Docker (docker-stable) (pull_request) Successful in 18m49s
issue-labels / release-notes (pull_request_target) Successful in 5s
test-multi-platform / arm64 (pull_request) Has been skipped
cascade / end-to-end (pull_request_target) Successful in 7s
cascade / forgejo (pull_request_target) Successful in 38s
27aa1c178d
Contributor

cascading-pr updated at actions/setup-forgejo#1045

cascading-pr updated at https://code.forgejo.org/actions/setup-forgejo/pulls/1045
mfenniak approved these changes 2026-07-18 02:01:08 +00:00
mfenniak left a comment

Looks great!

Looks great!
mfenniak referenced this pull request from a commit 2026-08-24 21:22:44 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No assignees
3 participants
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
forgejo/runner!1631
No description provided.