#386 signed SHA256SUMS in Gitea's publish.yml, but with BUILD_ON=github the release binaries and SHA256SUMS come from GitHub's ci.yml, so 27.1-rc.22 went out unsigned. 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, as on Gitea. The 27.1-rc.22 CHANGELOG entry said its downloads came with the signature; that line is gone.