Releases: attest build provenance; pin the AUR package's pgmp checksum
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
Releases had only SHA256SUMS.txt, which whoever could replace an asset could replace too. A new attest job in release.yml validates the assets as publish does and records a build provenance attestation for each of them (actions/attest-build-provenance, pinned by commit); it alone has id-token: write and attestations: write, and publish waits for it. docs/licensing.md and the README say how to check a download with gh attestation verify. The AUR server package's checksum for the pinned pgmp source was computed from a fresh download at release time. It now comes from deploy/windows-server/pgmp.sha256, the checksum the Windows build already checks the same download against, so makepkg rejects a changed tarball. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/d76d5dd0f933da7a336b68f9bc0500abfe2d718d
Open Releases: attest build provenance; pin the AUR package's pgmp checksum in the timeline