chore(release): point the one-shot signing-key sealer at the release-signing...
Self-hosted AI team: Claude Code, Codex and more, from your phone
Brought to you by:
fivedive
Originally created by: lodar
DIVE-8014, admin step 1 of the sealer (.github/workflows/seal-signing-keys.yml, merged in [#1623]).
Sets the two constants the sealer refuses to run without:
SEAL_TO_KEY = fip2YkDSQ2a9sXlJePgDX3e5VAPj0cPvojJoui75ogg=SEAL_TO_KEY_ID = 3380204578043523366Both are the key / key_id returned by:
gh api repos/5dive-ai/5dive/environments/release-signing/secrets/public-key
This is public data: GitHub holds the private half, so only GitHub can open what the sealer produces. Review it by running that command and comparing. Nothing else in the file changes (2 lines).
release-signing is set to deploy from main only, with no required reviewers and no wait timer (the nightly cut runs in it).
🤖 Generated with Claude Code
Ticket changed by: lodar