Gitea queues the macOS release job with an empty runner label when runs-on uses needs.prepare.outputs.runner, even though preparation succeeds and the macos-local runner is online. Read vars.MACOS_RUNNER directly when scheduling the release, as already used successfully by the macOS checks workflow. Remove the unused runner output; preparation still validates the configured label and gates the release, passing its validated commit and tag to the release steps.
Validation: 108 native JavaScript tests passed; the affected 10 workflow tests passed again after formatting. ESLint, YAML parsing, shell syntax and git diff checks pass. Live Gitea API confirmed run 1328 job 1944 had an empty label, runner 4 was online with macos-local, and run 1325 resolved the repository variable correctly.
After merge, cancel the waiting run 1328 and start a NEW manual macOS release to Hetzner run from main with tag=macos-v0.1.0. The existing tag does not need to be moved. The signed S3 release and user installation check remain pending; KAN-58 stays In Progress until that acceptance is complete.
Ticket: https://kanbangit.de/projects/1/tickets/58
Base and target: main, pulled with --ff-only at b4cd6a58087d499a86a40163e09b4d444e5517cf before creating fix/KAN-58-macos-runner-selection.
Gitea queues the macOS release job with an empty runner label when `runs-on` uses `needs.prepare.outputs.runner`, even though preparation succeeds and the `macos-local` runner is online. Read `vars.MACOS_RUNNER` directly when scheduling the release, as already used successfully by the macOS checks workflow. Remove the unused runner output; preparation still validates the configured label and gates the release, passing its validated commit and tag to the release steps.
Validation: 108 native JavaScript tests passed; the affected 10 workflow tests passed again after formatting. ESLint, YAML parsing, shell syntax and git diff checks pass. Live Gitea API confirmed run 1328 job 1944 had an empty label, runner 4 was online with `macos-local`, and run 1325 resolved the repository variable correctly.
After merge, cancel the waiting run 1328 and start a NEW manual `macOS release to Hetzner` run from `main` with `tag=macos-v0.1.0`. The existing tag does not need to be moved. The signed S3 release and user installation check remain pending; KAN-58 stays In Progress until that acceptance is complete.
Ticket: https://kanbangit.de/projects/1/tickets/58
Base and target: `main`, pulled with `--ff-only` at `b4cd6a58087d499a86a40163e09b4d444e5517cf` before creating `fix/KAN-58-macos-runner-selection`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Gitea queues the macOS release job with an empty runner label when
runs-onusesneeds.prepare.outputs.runner, even though preparation succeeds and themacos-localrunner is online. Readvars.MACOS_RUNNERdirectly when scheduling the release, as already used successfully by the macOS checks workflow. Remove the unused runner output; preparation still validates the configured label and gates the release, passing its validated commit and tag to the release steps.Validation: 108 native JavaScript tests passed; the affected 10 workflow tests passed again after formatting. ESLint, YAML parsing, shell syntax and git diff checks pass. Live Gitea API confirmed run 1328 job 1944 had an empty label, runner 4 was online with
macos-local, and run 1325 resolved the repository variable correctly.After merge, cancel the waiting run 1328 and start a NEW manual
macOS release to Hetznerrun frommainwithtag=macos-v0.1.0. The existing tag does not need to be moved. The signed S3 release and user installation check remain pending; KAN-58 stays In Progress until that acceptance is complete.Ticket: https://kanbangit.de/projects/1/tickets/58
Base and target:
main, pulled with--ff-onlyatb4cd6a58087d499a86a40163e09b4d444e5517cfbefore creatingfix/KAN-58-macos-runner-selection.