release/signing/release-files
Release artifacts are signed
Implements release/signing for the release-files artifact: it runs when the release publishes one (see artifacts).
| Severity | error |
| Tiers | 1 |
| Artifact | release-files |
| Scope | root |
| Kind | outcome |
| Source | library v0.3.1 |
| Selected by | fleetlint-recommended@v0.3.1 |
Requirement
The workflow that uploads the release files signs them or their checksums file (checksums.txt, SHA256SUMS): cosign keyless on GitHub and GitLab, key-based on Gitea, GoReleaser signs: or binary_signs:, or a detached gpg signature, and publishes the signatures with the release.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists || repo.artifacts.size() > 0Fix
Add sigstore/cosign-installer and cosign sign-blob --yes --bundle checksums.txt.sigstore.json checksums.txt to the release workflow (or signs: in .goreleaser.yaml) and upload the bundle with the release.
Agent instruction: Use the artifact’s own signing format when it has one. Otherwise add sigstore/cosign-installer and a signing step after the artifacts are built. Files: cosign sign-blob --yes --bundle checksums.txt.sigstore.json checksums.txt and upload the bundle. Container image: cosign sign --yes <image>@<digest> using the digest output of the build step, with id-token: write on the job.
See: https://fleetlint.org/baseline/#releases, https://docs.sigstore.dev/cosign/signing/signing_with_blobs/
Generated by fleetlint docs from catalog v0.3.1.