-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
FR: Ability to publish to Azure Artifacts #7860
Comments
Hi! the |
Improve hints when using the simple index URL instead of the upload URL in `uv publish`. This is the most common confusion when publishing, so we give it some extra care and put it more centrally in the CLI help. Fixes #7860
Improve hints when using the simple index URL instead of the upload URL in `uv publish`. This is the most common confusion when publishing, so we give it some extra care and put it more centrally in the CLI help. Fixes #7860
Improve hints when using the simple index URL instead of the upload URL in `uv publish`. This is the most common confusion when publishing, so we give it some extra care and put it more centrally in the CLI help. Fixes #7860
OMG you're RIGHT 👍👍👍 That's on me for blindly copying the Twine setup link from the Azure devops docs page - without checking it was correct. Bless u It works like a charm now
You're a gem, good PR too it'll stop people like me coming here in future lol. I'll let that pull close the issue. Cheers |
Improve hints when using the simple index URL instead of the upload URL in `uv publish`. This is the most common confusion when publishing, so we give it some extra care and put it more centrally in the CLI help. Fixes #7860 --------- Co-authored-by: Zanie Blue <[email protected]>
I ended up using
and avoiding keyring as it gave me a nasty error. |
Hello,
My apologies if this is already a feature, and I'm misunderstanding how to publish.
The ability to publish a wheel package to Azure artifacts would be greatly welcomed. I hate using GitHub Issue's to ask for help so I'm potentially writing this under the guise of a Feature Request.
At the moment
uv publish
can attempt to publish to Artifacts:Using:
uv publish --publish-url https://pkgs.dev.azure.com/Company/Package/_packaging/Feed/pypi/simple/ --verbose --username VssSessionToken
Gets us:
While alternativly:
uv publish --publish-url https://[email protected]/Company/Package/_packaging/Feed/pypi/simple/ --verbose
Gets us
This is with using
pyproject.toml
to configure "keyring-provider" and "extra-index-url" under[tool.uv]
which appears to be working nicely.Alternativly, if anyone has any ideas on how to bodge my config into letting me upload a package to Artifacts, that would be very welcomed!
If this is just user-error then I'll pretend this Issue was actually a Documentation idiotification Feature Request :)
Thanks!
The text was updated successfully, but these errors were encountered: