-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Build attestations improvements #501
base: main
Are you sure you want to change the base?
Conversation
@@ -245,6 +245,12 @@ jobs: | |||
build/pythonbuild validate-distribution ${EXTRA_ARGS} dist/*.tar.zst | |||
- name: Generate attestations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops! Thank you!
.github/workflows/release.yml
Outdated
uses: actions/attest-build-provenance@v2 | ||
if: ${{ github.event.inputs.dry-run == 'false' }} | ||
with: | ||
subject-path: dist/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm worried about the 1024 subject limit https://github.com/actions/attest-build-provenance?tab=readme-ov-file#subject-limits
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(1131 artifacts in the last release)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. We could arguably divide the attestation groups by python versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adjusted the glob to skip .sha256 files as I don't think they benefit from attestation. Given this purely from a count perspective we can stay within the quota ~564
Note, the glob is targeted at minimatch js library which is what actions/glob supports which this action uses underneath.
Per #343 (comment)