27.1-rc.22 shipped without SHA256SUMS.minisig. #386 added signing to Gitea's publish.yml, but this repo builds releases on GitHub (BUILD_ON=github), and GitHub's ci.yml makes the binaries and SHA256SUMS, with no signing step.
.github/workflows/ci.yml, binaries job: signs out/SHA256SUMS with MINISIGN_SECRET_KEY (trusted comment inbuxa <tag>, as on Gitea and in inbuxa-migrate) and attaches SHA256SUMS.minisig. With no key it warns and the release stays unsigned. The release copy to GitHub already takes every asset, so it carries the signature over.
CHANGELOG: the 27.1-rc.22 entry no longer claims signed downloads.
Needs John: add MINISIGN_SECRET_KEY to the GitHub repo inbuxa/inbuxa-server (the same key as inbuxa-migrate's). The Gitea secret exists, but the GitHub one doesn't.
Checked locally: YAML parses, version.py --changelog, the four fork checks and the release tool tests.
27.1-rc.22 shipped without `SHA256SUMS.minisig`. #386 added signing to Gitea's `publish.yml`, but this repo builds releases on GitHub (`BUILD_ON=github`), and GitHub's `ci.yml` makes the binaries and `SHA256SUMS`, with no signing step.
- `.github/workflows/ci.yml`, binaries job: signs `out/SHA256SUMS` with `MINISIGN_SECRET_KEY` (trusted comment `inbuxa <tag>`, as on Gitea and in inbuxa-migrate) and attaches `SHA256SUMS.minisig`. With no key it warns and the release stays unsigned. The release copy to GitHub already takes every asset, so it carries the signature over.
- CHANGELOG: the 27.1-rc.22 entry no longer claims signed downloads.
**Needs John:** add `MINISIGN_SECRET_KEY` to the GitHub repo `inbuxa/inbuxa-server` (the same key as inbuxa-migrate's). The Gitea secret exists, but the GitHub one doesn't.
Checked locally: YAML parses, `version.py --changelog`, the four fork checks and the release tool tests.
#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.
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.
27.1-rc.22 shipped without
SHA256SUMS.minisig. #386 added signing to Gitea'spublish.yml, but this repo builds releases on GitHub (BUILD_ON=github), and GitHub'sci.ymlmakes the binaries andSHA256SUMS, with no signing step..github/workflows/ci.yml, binaries job: signsout/SHA256SUMSwithMINISIGN_SECRET_KEY(trusted commentinbuxa <tag>, as on Gitea and in inbuxa-migrate) and attachesSHA256SUMS.minisig. With no key it warns and the release stays unsigned. The release copy to GitHub already takes every asset, so it carries the signature over.Needs John: add
MINISIGN_SECRET_KEYto the GitHub repoinbuxa/inbuxa-server(the same key as inbuxa-migrate's). The Gitea secret exists, but the GitHub one doesn't.Checked locally: YAML parses,
version.py --changelog, the four fork checks and the release tool tests.