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
2 Commits
Author SHA1 Message Date
jcoffey-dev 2e0a83a982 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
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)
2026-11-17 12:20:13 -07:00
jcoffey-dev 9fe3686135 publish: sign SHA256SUMS with minisign
(cherry picked from commit e44dfeed24)
2026-11-17 12:19:50 -07:00