Add a uv publish command

[zanieb]

e.g., to publish the project to PyPI.

This is a pretty large, but well isolated project — if you've contributed previously and are interested in working on it let me know.

[pplmx]

Add uv build and uv test too?

[zanieb]

Those are both out of scope for this issue — though uv build should be trivial once uv publish is set up. See #1510 for the relevant tracking issue there.

[Zaf4]

I was going to open the same issue I have been using poetry for publishing. Would be great to fully switch to uv for everything.

[woodruffw]

Hi all! I'm neither a maintainer of PyPI nor twine, but I'm an active contributor to both who has touched a lot of the components related to uploading/API tokens/etc. It's very exciting to see uv consider adding publishing support!

A couple of things that might be worth considering as part of an implementation here:

• PyPI and TestPyPI both support trusted publishing, i.e. credentialless package publishing via OIDC. This is handled transparently at the API token issuance layer to avoid any changes to PyPI's authentication parameters, but a future uv publish command could avoid the need for a separate token exchange step by performing the token exchange internally.
• PyPI and TestPyPI are nearing the completion of initial support for PEP 740, i.e. index support for digital attestations over packages. twine has support for detecting and uploading attestations; a future uv publish command could consider adding support as well 🙂

I'm happy to provide more details on the above or anything else related to publishing, to those interested. Just let me know!

[andrlik]

Adding this comment to the correct issue. 🤦

Would be good to mimic the rye publish command where it prompts you to encrypt your PyPI token with a password.

[konstin]

uv publish is now implemented. It supports token authentication (for PyPI), username/password authentication, keyring integration and trusted publishing support for GitHub Actions + PyPI (publishing without manually configuration a secret in GitHub Actions). In the next release, it will ship in preview mode (pass --preview to use it), as we might still need to make minor adjustments to the CLI outside of our usual stability policy.

If you are running into any problems, please open an issue! Especially for authentication with private registries feedback would be invaluable.

[juan-abia]

Related @konstin:
#8221