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.
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)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Backports release signing (#386, #396) to release/2026, so 2026.x releases get
SHA256SUMS.minisigthe way 27.1 RCs have since rc.23. 2026.11.11 and 2026.11.17 went out unsigned.publish.yml(BUILD_ON != github): signs/out/SHA256SUMSand attaches the signature.ci.ymlbinaries job (BUILD_ON=github, the current path): signsout/SHA256SUMSand attaches the signature.Both conflicted only because release/2026 attaches no relay binaries; the asset lists keep 2026's files and add
SHA256SUMS.minisig. WithoutMINISIGN_SECRET_KEYeach 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.