release/checksums
Releases publish checksums
| Severity | warning |
| Tiers | 1 |
| Stacks | any |
| Scope | root |
| Kind | outcome |
| Source | library v0.2.0 |
| Selected by | fleetlint-recommended@v0.2.0 |
Requirement
A checksums file (sha256) covering every artifact is uploaded with the release, and is what gets signed. A container image pushed to a registry is addressed by its digest, and a package published to npm, PyPI, crates.io or RubyGems gets its digest recorded by the registry; neither needs a separate file.
Why
Checksums let a downloader verify integrity even without signature tooling.
Applies when
release.exists && tagged_workflows().size() > 0Fix
Generate checksums.txt with sha256sum in the release job and upload it.
Agent instruction: Add sha256sum dist/* > dist/checksums.txt before the upload step and include dist/checksums.txt in the release assets.
See: https://fleetlint.org/baseline/#releases
Generated by fleetlint docs from catalog v0.2.0.