-
Notifications
You must be signed in to change notification settings - Fork 18
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
Migrate to uv
builds
#126
Migrate to uv
builds
#126
Conversation
After this PR is merged, I'd like to cut a new release (which is a nice test if the new |
I'm in transit today. If there are any finishing touches you want to do then please go ahead without me. |
This looks good to me except for one point: I'm not entirely convinced that we should include |
OK ready to go. You're welcome to squash if you want when merging. |
Thanks @cboulay! |
Note: Using "trusted publisher" between pypi <--> GitHub, the
uv build
anduv publish
steps are quite simple and don't require tokens or an intermediate artifact.__version__.py
file written upon build based on the tag. If the most recent commit is beyond the latest tag then the version will be appended with a commit hash.