Sign 2026.x release downloads with minisign #417

Merged
jcoffey-dev merged 2 commits from ci/minisign-2026 into release/2026 2026-11-17 19:30:17 +00:00
Owner

Backports release signing (#386, #396) to release/2026, so 2026.x releases get SHA256SUMS.minisig the way 27.1 RCs have since rc.23. 2026.11.11 and 2026.11.17 went out unsigned.

  • Gitea publish.yml (BUILD_ON != github): signs /out/SHA256SUMS and attaches the signature.
  • GitHub ci.yml binaries job (BUILD_ON=github, the current path): signs out/SHA256SUMS and attaches the signature.

Both conflicted only because release/2026 attaches no relay binaries; the asset lists keep 2026's files and add SHA256SUMS.minisig. Without MINISIGN_SECRET_KEY each warns and the release stays unsigned. The key is a repository secret on GitHub, so tags cut from release/2026 already see it.

No version change here. The first signed 2026.x release is the next one; its CHANGELOG entry should say the downloads now come with SHA256SUMS.minisig.

Checked locally: both workflow files parse, fork checks pass.

Backports release signing (#386, #396) to release/2026, so 2026.x releases get `SHA256SUMS.minisig` the way 27.1 RCs have since rc.23. 2026.11.11 and 2026.11.17 went out unsigned. - Gitea `publish.yml` (BUILD_ON != github): signs `/out/SHA256SUMS` and attaches the signature. - GitHub `ci.yml` binaries job (BUILD_ON=github, the current path): signs `out/SHA256SUMS` and attaches the signature. Both conflicted only because release/2026 attaches no relay binaries; the asset lists keep 2026's files and add `SHA256SUMS.minisig`. Without `MINISIGN_SECRET_KEY` each warns and the release stays unsigned. The key is a repository secret on GitHub, so tags cut from release/2026 already see it. No version change here. The first signed 2026.x release is the next one; its CHANGELOG entry should say the downloads now come with `SHA256SUMS.minisig`. Checked locally: both workflow files parse, fork checks pass.
jcoffey-dev added 2 commits 2026-11-17 19:20:34 +00:00
(cherry picked from commit e44dfeed24)
Sign SHA256SUMS on GitHub builds too (2026.x)
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 9m5s
2e0a83a982
With BUILD_ON=github the release binaries and SHA256SUMS come from
GitHub's ci.yml, so 2026.x releases (2026.11.11, 2026.11.17) went out
without a signature. The binaries job now signs SHA256SUMS with the same
MINISIGN_SECRET_KEY and attaches SHA256SUMS.minisig. With no key it
warns and the release stays unsigned. release/2026 attaches no relay
binaries, so its asset list only gains the signature.

(cherry picked from commit 35cc4d6ed9)
jcoffey-dev merged commit 721055b3aa into release/2026 2026-11-17 19:30:17 +00:00
jcoffey-dev deleted branch ci/minisign-2026 2026-11-17 19:30:17 +00:00
Sign in to join this conversation.