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

Add action to upload the wheel and tar-zipped distributions #1136

Closed
wants to merge 2 commits into from

Conversation

ericwb
Copy link
Member

@ericwb ericwb commented May 2, 2024

We already publish to PyPI our packages. It is also useful to publish our binaries as artifacts here on GitHub. This action will build and publish release files as artifacts in the current release.

It runs whenever a new release is published.

This change also adds attestation of the artifacts so that users can verify the binary is the authentic one produced by our build.

More info on attestation here:
https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/

We already publish to PyPI our packages. It is also useful to
publish our binaries as artifacts here on GitHub. This action
will build and publish release files as artifacts in the current
release.

It runs whenever a new release is published.

This change also adds attestation of the artifacts so that users
can verify the binary is the authentic one produced by our build.

More info on attestation here:
https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/

Signed-off-by: Eric Brown <eric_wade_brown@yahoo.com>
@sigmavirus24
Copy link
Member

There's almost no value in doing this. Twine and PyPI are actively implementing support for attestations

@ericwb
Copy link
Member Author

ericwb commented May 2, 2024

I know PyPI has been working on this for a while. Is it available yet? But yes, I understand how this can be redundant to have two destinations for artifacts and two ecosystems to attest them. It definitely feels like GitHub is attempting to a one-stop shop for all things code. I thought it was nice that you can attest the binaries with GitHub's CLI. Does Pip have plans for the same?

In any case, I can close this as I don't want to create confusion on where to obtain binaries and how to attest them.

@ericwb
Copy link
Member Author

ericwb commented May 2, 2024

Thinking about this more, totally agree. It's a bad idea to have two source repositories to fetch packages, each with it's own attestation.

@ericwb ericwb closed this May 2, 2024
@ericwb ericwb deleted the assets branch May 2, 2024 18:25
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.

None yet

2 participants