ci: the release's version and publish run only on the server's runner, the release key sealed with a key only it has #241

Merged
HumanBean merged 1 commit from HumanBean/LongshotLauncher:ci/sealed-release-key into main 2026-11-21 21:25:23 +00:00
Owner

Summary

This is the launcher's half of Longshot #2123. Both repositories sign with the organization secret RELEASE_SIGNING_KEY. A runner lent by someone else could add quick to its labels and take Sign and publish, and with it the key.

  • version and publish now ask for label deploy, which only the server's quick runner carries.
  • publish reads RELEASE_SIGNING_KEY_SEALED and opens it with the server's seal.key, mounted only on that runner. The sealing is the same as Longshot's scripts/ci_secret.sh, inlined here as one openssl line. A runner without seal.key stops with "no /run/magicbean-secrets/seal.key" and signs nothing.
  • RELEASING.md and docs/releases.md name the new secret.

Testing

Tested: nothing ran here; the workflow only runs on the forge. The change was checked by reading it.

Still to test:

  • Server: once the server setup and the sealed secret are in (Longshot #2123's order), the next launcher nightly's Sign and publish runs on unraid-quick-1 and passes verify (by hand, in the run's log).

Risks

If it merges before the server and the secret are ready, launcher nightlies fail until they are. Nothing is published wrongly. Reverting is enough. Players notice nothing.

🤖 Generated with Claude Code

## Summary This is the launcher's half of [Longshot #2123](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/2123). Both repositories sign with the organization secret `RELEASE_SIGNING_KEY`. A runner lent by someone else could add `quick` to its labels and take *Sign and publish*, and with it the key. - `version` and `publish` now ask for label **`deploy`**, which only the server's quick runner carries. - publish reads **`RELEASE_SIGNING_KEY_SEALED`** and opens it with the server's `seal.key`, mounted only on that runner. The sealing is the same as Longshot's `scripts/ci_secret.sh`, inlined here as one `openssl` line. A runner without `seal.key` stops with "no /run/magicbean-secrets/seal.key" and signs nothing. - `RELEASING.md` and `docs/releases.md` name the new secret. ## Testing **Tested:** nothing ran here; the workflow only runs on the forge. The change was checked by reading it. **Still to test:** - Server: once the server setup and the sealed secret are in (Longshot #2123's order), the next launcher nightly's *Sign and publish* runs on `unraid-quick-1` and passes `verify` (by hand, in the run's log). ## Risks If it merges before the server and the secret are ready, launcher nightlies fail until they are. Nothing is published wrongly. Reverting is enough. Players notice nothing. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ci: the release's version and publish run only on the server's runner, and the release key is sealed with a key only it has
All checks were successful
CI / Compile and test (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 4s
c0d49322f2
The same as Longshot's: label deploy instead of quick, and RELEASE_SIGNING_KEY_SEALED opened with
the server's seal.key (Longshot's scripts/ci_secret.sh), so a runner lent by someone else that
takes the job can't open the release key.

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

Possibly related, for context:

  • PR MagicBeanDev/Longshot#2123 WIP: ci: the release and deploy jobs run only on the server's runner, their secrets sealed with a key only it has — Coordinated sealed-secret and deploy-runner changes; must land together
Possibly related, for context: - PR MagicBeanDev/Longshot#2123 WIP: ci: the release and deploy jobs run only on the server's runner, their secrets sealed with a key only it has — Coordinated sealed-secret and deploy-runner changes; must land together
HumanBean changed title from WIP: ci: the release's version and publish run only on the server's runner, the release key sealed with a key only it has to ci: the release's version and publish run only on the server's runner, the release key sealed with a key only it has 2026-11-21 21:25:13 +00:00
HumanBean deleted branch ci/sealed-release-key 2026-11-21 21:25:23 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 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
MagicBeanDev/LongshotLauncher!241
No description provided.