Does your org run a self-managed version of GitLab and publish your own #Python packages to @pypi ?

If you want to try out an alpha of Trusted Publishing for GitLab Self-Managed instances, let me know via DM - I'm collecting interest now, and should have something to show soon.

@miketheman @pypi cc @vagrantc maybe the Reproducible Builds folks are interested in this? :)
@sethmlarson @miketheman @pypi @vagrantc I'm interested in (once again) publishing my own signed packages on PyPI -- does this happen to help there?

@meejah @sethmlarson

The overall concepts are detailed here: https://docs.pypi.org/trusted-publishers/

TL,DR: using OIDC to generate short-lived access tokens to publish from known publishers, instead of holding on to long-lived API Tokens

Getting Started - PyPI Docs

@miketheman @pypi

What sort of "Trusted Publishing" does this do?

Signed packages? Provide sufficient information to attempt and verify #ReproducibleBuilds ? Chains of Provenance?

@vagrantc TL,DR: using OIDC to generate short-lived access tokens to publish from known publishers.
Lots of docs: https://docs.pypi.org/trusted-publishers/
Getting Started - PyPI Docs

@miketheman @pypi Not a Gitlab user, just running a small gitea instance.

Is there an issue, blog or PR I could follow to read more about your approach once it is published?

Introducing 'Trusted Publishers' - The Python Package Index Blog

Announcing a new, more secure way to publish to PyPI

@miketheman thank you for the link; I have been looking into adding “trusted publishing” as defined by the WG to a primarily self hosted platform and this will the final puzzle piece to make that reasonable for the deployment scenario.

Thank you for your effort and good luck for the work ahead!