ci: the release build runs only on runners labelled release #83

Merged

HumanBean merged 1 commit from HumanBean/LongshotLauncher:ci/release-runner into main

2026-11-15 08:06:33 +00:00

HumanBean commented

2026-11-15 06:59:47 +00:00

Owner

The release build asks for ubuntu-latest, the label every pull request's checks use, so it can land on any runner and a runner kept for releases picks up CI too. This moves it to a label of its own, release, as Longshot does in MagicBeanDev/Longshot#728.

release.yml: The launcher, both systems runs on release. The version and Sign and publish stay on quick; ci.yml is unchanged.
The labels and how to register a release runner are in Longshot's docs/forgejo-runners.md (changed in #728), which this repository's docs already link to.

Risk: a release, nightlies included, waits while no release runner is online (one is registered: charles-linux). Revert, or add the label to another runner, to undo.

Tested: python -I tests/test_launcher_core.py (1044 checks) and python -I tests/test_release.py pass; actionlint 1.7.12 with Longshot's config finds nothing. The first nightly after merge is the real test: its build job should run on the release runner.

🤖 Generated with Claude Code

The release build asks for `ubuntu-latest`, the label every pull request's checks use, so it can land on any runner and a runner kept for releases picks up CI too. This moves it to a label of its own, `release`, as Longshot does in [MagicBeanDev/Longshot#728](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/728). - `release.yml`: *The launcher, both systems* runs on `release`. *The version* and *Sign and publish* stay on `quick`; `ci.yml` is unchanged. - The labels and how to register a `release` runner are in Longshot's `docs/forgejo-runners.md` (changed in #728), which this repository's docs already link to. **Risk:** a release, nightlies included, waits while no `release` runner is online (one is registered: charles-linux). Revert, or add the label to another runner, to undo. **Tested:** `python -I tests/test_launcher_core.py` (1044 checks) and `python -I tests/test_release.py` pass; actionlint 1.7.12 with Longshot's config finds nothing. The first nightly after merge is the real test: its build job should run on the `release` runner. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

HumanBean added 1 commit

2026-11-15 06:59:48 +00:00

ci: release builds run only on runners labelled release

CI / Compile and test (pull_request) Has been skipped

Details

CI / Conventional Commit title (pull_request) Successful in 4s

Details

9df098f90d

Co-Authored-By: Claude Opus 5.5 <[email protected]>

HumanBean referenced this pull request from MagicBeanDev/Longshot

2026-11-15 06:59:59 +00:00

ci: release builds run only on runners labelled release #728

HumanBean merged commit 9254499ed0 into main

2026-11-15 08:06:33 +00:00

HumanBean deleted branch ci/release-runner

2026-11-15 08:06:33 +00:00

HumanBean referenced this pull request from a commit

2026-11-15 08:06:35 +00:00

ci: the release build runs only on runners labelled release (#83)

HumanBean referenced this pull request from a commit

2026-11-15 18:15:36 +00:00

ci: release builds run only on runners labelled release (#728)

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

MagicBeanDev/LongshotLauncher!83

No description provided.

Rows
Columns