Skip to content
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

Attest build provenance #431

Merged
merged 5 commits into from
May 16, 2024
Merged

Attest build provenance #431

merged 5 commits into from
May 16, 2024

Conversation

nicoddemus
Copy link
Member

@nicoddemus nicoddemus commented May 16, 2024

This uses the new build provenance support added in build-and-inspect-python-package 2.5.0.

@nicoddemus
Copy link
Member Author

@nicoddemus nicoddemus merged commit bbeeb6d into main May 16, 2024
16 checks passed
@nicoddemus nicoddemus deleted the build-provenance branch May 16, 2024 10:55
nicoddemus added a commit to pytest-dev/pytest that referenced this pull request May 16, 2024
This uses the new build provenance support added in [build-and-inspect-python-package 2.5.0](https://github.com/hynek/build-and-inspect-python-package/blob/main/CHANGELOG.md#250---2024-05-13).

More information: https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/

Tested also in pytest-dev/pytest-mock#431.

Note: even though it is technically necessary only for the `deploy` workflow, as the `test` workflow does not publish its packages, decided to always attest the provenance in both cases to avoid any surprises related to this (say a misconfiguration) when deploying.
nicoddemus added a commit to pytest-dev/pytest that referenced this pull request May 17, 2024
Use the new build provenance support added in [build-and-inspect-python-package 2.5.0](https://github.com/hynek/build-and-inspect-python-package/blob/main/CHANGELOG.md#250---2024-05-13).

More information: https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/

Tested also in pytest-dev/pytest-mock#431.

Note: even though it is technically necessary only for the `deploy` workflow, as the `test` workflow does not publish its packages, decided to always attest the provenance in both cases to avoid any surprises related to this (say a misconfiguration) when deploying.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant