Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

release: fail the checksums signs entry closed and gate the fallback on the key

Claude12cf3541aac1
diff --git a/CLAUDE.md b/CLAUDE.md
index 8f3ba2b4..ef281da5 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -495,12 +495,15 @@ git -C .tmp/release-<tag> tag -a <tag> -m "<tag>"
git -C .tmp/release-<tag> push origin <tag>
cd .tmp/release-<tag>/cli/beacon
goreleaser check
-GITHUB_TOKEN="${GITHUB_TOKEN:-$(gh auth token)}" HOMEBREW_TAP_TOKEN="${HOMEBREW_TAP_TOKEN:-$(gh auth token)}" goreleaser release --clean --parallelism 1
+GITHUB_TOKEN="${GITHUB_TOKEN:-$(gh auth token)}" HOMEBREW_TAP_TOKEN="${HOMEBREW_TAP_TOKEN:-$(gh auth token)}" goreleaser release --clean --parallelism 1 $([ -n "${BEACON_LINUX_SIGNING_KEY_FPR:-}" ] || echo --skip=sign)
```
The `signs` entry signs `checksums.txt` with the key named by `BEACON_LINUX_SIGNING_KEY_FPR` (and `GNUPGHOME`
-holding it, as `release.yml` sets up). Without it gpg fails at the sign step, before anything is published, so a
-local release must either export both or add `--skip=sign`, which publishes an unsigned `checksums.txt`.
+holding it, as `release.yml` sets up). The command above adds `--skip=sign` when the variable is unset, which
+publishes an unsigned `checksums.txt`; once `release-key.fingerprint` pins a key, installers refuse that release,
+so a pinned fallback release must export both. Run without either, the entry fails closed at the sign step (gpg
+is asked for a key named `BEACON_LINUX_SIGNING_KEY_FPR-unset`, never a default key) before anything is published.
+GoReleaser OSS has no `if`/`skip` on `signs`, so every snapshot invocation passes `--skip=sign` itself.
After GoReleaser succeeds, verify both the GitHub release and the Homebrew tap:
diff --git a/cli/beacon/.goreleaser.yaml b/cli/beacon/.goreleaser.yaml
index 04c1379e..fa48c4fb 100644
--- a/cli/beacon/.goreleaser.yaml
+++ b/cli/beacon/.goreleaser.yaml
@@ -211,7 +211,11 @@ checksum:
algorithm: sha256
# Signs checksums.txt with the Linux release key release.yml imports (GNUPGHOME and
-# BEACON_LINUX_SIGNING_KEY_FPR); release.yml passes --skip=sign when no key is configured.
+# BEACON_LINUX_SIGNING_KEY_FPR); release.yml passes --skip=sign when no key is configured, and
+# every snapshot invocation passes it too. GoReleaser OSS has no `if`/`skip` on signs, so without
+# --skip=sign and without the variable this fails closed: gpg is asked for a key named
+# "BEACON_LINUX_SIGNING_KEY_FPR-unset", reports "No secret key" and never falls back to a default
+# key; signing runs before publish, so nothing is uploaded.
# GoReleaser uploads into a draft and publishes last, so checksums.txt.sig is on the release
# before it becomes latest. Its checksums.txt is rewritten deterministically at publish, so the
# signature still matches; finalize extends the file and signs it again.
@@ -228,7 +232,7 @@ signs:
- --passphrase-fd
- "0"
- --local-user
- - '{{ envOrDefault "BEACON_LINUX_SIGNING_KEY_FPR" "" }}'
+ - '{{ envOrDefault "BEACON_LINUX_SIGNING_KEY_FPR" "BEACON_LINUX_SIGNING_KEY_FPR-unset" }}'
- --output
- "${signature}"
- --detach-sign