-
-
Notifications
You must be signed in to change notification settings - Fork 124
Add GitHub artifact attestations to release workflow #1494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1494 +/- ##
=======================================
Coverage 91.51% 91.51%
=======================================
Files 87 87
Lines 18153 18153
=======================================
Hits 16612 16612
Misses 1541 1541 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
58d9ed8 to
1e9d0b4
Compare
📦 Cargo Bloat ComparisonBinary size change: +0.00% (22.5 MiB → 22.5 MiB) Expand for cargo-bloat outputHead Branch ResultsBase Branch Results |
1e9d0b4 to
f4513c6
Compare
Enable GitHub artifact attestations via cargo-dist's native support.
Consumers can verify release artifacts were built by CI:
gh attestation verify <artifact> --repo j178/prek
Closes j178#1493
f4513c6 to
1e015f5
Compare
|
Thanks! I think it would also be great to add attestation for our |
|
Ah, I missed that. I'll make a follow up PR :) |
Closes #1493
Adds actions/attest-build-provenance to the release workflow so consumers can verify artifacts were built by CI:
GitHub already generates release attestations that verify file integrity (checksums), but build provenance additionally proves the artifacts were produced by the CI workflow rather than uploaded manually.