-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update configuration to support CI-compatible versioning without manual interaction #11
Comments
…-bump #11 💚 support automatic dev versioning for ci builds
…mization #11 💚 fix overzealous step skipping optimization
Now, updates using This will likely be automated into the lifecycle eventually, but now we don't have to do this and deal with the failing CI manual builds when they are missed (not exactly something most of us are used to having to tinker with pre-build). |
Not to necro a closed ticket, but I think i'm a bit confused on this @d-ryan-ashcraft ; the page you linked to is the policy for uv's versioning itself (I.e. the version rules that astral uses for uv releases) but it seems like you're speaking more to the capabilities that bump2version https://github.com/c4urself/bump2version and tools like it provide: i.e. bumping the version of an application or library based on e.g. the commit messages etc. I wasn't aware of uv providing support for that kind of version management at all. It's interesting to see the discussion on the linked GH issue. The conversation there is admittedly confusing to me though, as uv version command appears to report the version of uv itself, rather than trying to bump the version of the managed project/package. |
I was trying to note that there isn't strong support for versioning schemes typically found in package/project manager and build tools. It sounds like it is coming; it's just not there yet. This seems like a function of Perhaps I linked a non-optimal page for that point. |
Got ya; I think I had just categorized that capability into something that uv didn't try to do; i.e. not the tool for that. |
uv
does not currently supportdev
versions or full semantic versioning. They intend to get there, but as of version 0.5.21, they aren't there yet:Additionally, it is not a straightforward update to achieve this functionality.
In the meantime, we need something to enable CI builds to not require manual intervention.
The text was updated successfully, but these errors were encountered: