Skip to content

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

Merge origin/main into claude/issue-907-linux-signing

Claudefbccb833f016
diff --cc .github/workflows/release.yml
index f14de189,e3f91ca2..e6406d89
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@@ -97,7 -93,8 +110,9 @@@ jobs
env:
GITHUB_TOKEN: ${{ github.token }}
HOMEBREW_TAP_TOKEN: ${{ secrets.HOMEBREW_TAP_TOKEN }}
+ NFPM_PASSPHRASE: ${{ secrets.BEACON_LINUX_SIGNING_KEY_PASSPHRASE }}
+ GORELEASER_CURRENT_TAG: ${{ github.ref_name }}
+ GORELEASER_PREVIOUS_TAG: ${{ steps.tags.outputs.previous }}
run: goreleaser release --clean --parallelism 1
package:
diff --cc CLAUDE.md
index 4f16ceea,ee71aeb7..559c93ba
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@@ -287,15 -291,13 +292,17 @@@ A pushed `v*` tag runs the full releas
appends the `.pkg`, `.msi` and `install.sh` to `checksums.txt` from the released bytes and
records a GitHub build-provenance attestation (Sigstore, keyless, through the
workflow's OIDC token) for every file `checksums.txt` lists. It needs
- `id-token: write` and `attestations: write` and no `release`-environment secrets.
+ `id-token: write` and `attestations: write`, and runs in the `release`
+ environment only so that, when `BEACON_LINUX_SIGNING_KEY` exists, it can sign
+ the final `checksums.txt` as `checksums.txt.sig` and attach the public key as
+ `beacon-release-key.{asc,gpg}`. Anything else that rewrites `checksums.txt`
+ must come before that step.
- Every third-party action in `release.yml` and `release-extension.yml` is pinned to
- a full commit SHA with the version in a trailing comment, because these jobs hold
- the signing secrets. Bump them by SHA, never back to a tag.
+ Every third-party action in `release.yml`, `release-extension.yml` and
+ `npm-publish-sdk.yml` is pinned to a full commit SHA with the version in a
+ trailing comment, because these jobs hold the signing secrets or, for the SDK,
+ the `id-token` npm's trusted publisher accepts. Bump them by SHA, never back to
+ a tag.
Required `release`-environment secrets: `HOMEBREW_TAP_TOKEN`,
`DEVELOPER_ID_APP_CERT_P12`, `DEVELOPER_ID_APP_CERT_PASSWORD`,