Thanks to visit codestin.com
Credit goes to github.com

Skip to content

CI: Add GitHub artifact attestations to package distribution #28273

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

Merged
merged 2 commits into from
May 29, 2024

Conversation

matthewfeickert
Copy link
Contributor

PR summary

This PR is related to scientific-python/summit-2024#9 so cc @QuLogic for review. c.f. scikit-hep/pyhf#2473 for reference.

PR checklist

@github-actions github-actions bot added the CI: Run cibuildwheel Run wheel building tests on a PR label May 21, 2024
@matthewfeickert matthewfeickert changed the title ci: Add GitHub artifact attestations to package distribution CI: Add GitHub artifact attestations to package distribution May 21, 2024
@matthewfeickert matthewfeickert force-pushed the ci/add-artifact-attestations branch from 427fe83 to e28c1f4 Compare May 22, 2024 00:03
@@ -79,7 +79,7 @@ repos:
- id: yamllint
args: ["--strict", "--config-file=.yamllint.yml"]
- repo: https://github.com/python-jsonschema/check-jsonschema
rev: 0.28.1
rev: 0.28.4
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without this pre-commit hook update, pre-commit will fail as attestation is a newer permissions key. To keep this atomic I'm only updating this hook instead of all of them.

@tacaswell tacaswell added this to the v3.9.1 milestone May 22, 2024
@matthewfeickert matthewfeickert force-pushed the ci/add-artifact-attestations branch from e28c1f4 to a5e6e93 Compare May 27, 2024 19:54
@QuLogic
Copy link
Member

QuLogic commented May 27, 2024

This of course doesn't run unless we're tagging a release. Does it make sense to have a separate job that always runs to do the attestation? Or is that overkill?

@matthewfeickert
Copy link
Contributor Author

matthewfeickert commented May 27, 2024

Does it make sense to have a separate job that always runs to do the attestation? Or is that overkill?

@QuLogic My understanding from scikit-hep/pyhf#2473 is that while there's nothing wrong with creating attestations for every run of the CI, there could value in keeping the number of attestations to a human readable number that just correspond to releases. As there doesn't seem to be a way to delete attestation records from GitHub I would advocate having attestations be 1-to-1 with published artifacts.

@tacaswell
Copy link
Member

I think starting with just releases is the right call.

@matthewfeickert
Copy link
Contributor Author

Example of a release of Awkward Array with signed artifacts, and how from a maintainer perspective keeping a clean visual list of release-only attestations would be nice:

scikit-hep/awkward#3126 (comment)

@QuLogic QuLogic merged commit 394761a into matplotlib:main May 29, 2024
46 checks passed
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request May 29, 2024
@matthewfeickert matthewfeickert deleted the ci/add-artifact-attestations branch May 29, 2024 19:06
ksunden added a commit that referenced this pull request May 29, 2024
…273-on-v3.9.x

Backport PR #28273 on branch v3.9.x (CI: Add GitHub artifact attestations to package distribution)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: Run cibuildwheel Run wheel building tests on a PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants