Skip to content
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

Closed
d-ryan-ashcraft opened this issue Jan 21, 2025 · 4 comments
Assignees
Milestone

Comments

@d-ryan-ashcraft
Copy link
Contributor

d-ryan-ashcraft commented Jan 21, 2025

uv does not currently support dev versions or full semantic versioning. They intend to get there, but as of version 0.5.21, they aren't there yet:

Versioning
uv uses a custom versioning scheme in which the minor version number is bumped for breaking changes, and the patch version number is bumped for bug fixes, enhancements, and other non-breaking changes.

uv does not yet have a stable API; once uv's API is stable (v1.0.0), the versioning scheme will adhere to Semantic Versioning.

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.

@d-ryan-ashcraft d-ryan-ashcraft self-assigned this Jan 21, 2025
@d-ryan-ashcraft d-ryan-ashcraft added this to the 0.1.7 milestone Jan 21, 2025
d-ryan-ashcraft added a commit that referenced this issue Jan 21, 2025
…-bump

#11 💚 support automatic dev versioning for ci builds
d-ryan-ashcraft added a commit that referenced this issue Jan 21, 2025
…mization

#11 💚 fix overzealous step skipping optimization
@d-ryan-ashcraft
Copy link
Contributor Author

Now, updates using bump-my-version in the CI build only for the dev branch.

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).

@nivintw
Copy link
Collaborator

nivintw commented Jan 24, 2025

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. uv version, as far as I can tell, is only mentioned because the command currently exists, and so to add the requested feature with that same command name would result in breaking changes

@d-ryan-ashcraft
Copy link
Contributor Author

d-ryan-ashcraft commented Jan 24, 2025

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 uv being a relatively young tool (not a value judgment).

Perhaps I linked a non-optimal page for that point.

@nivintw
Copy link
Collaborator

nivintw commented Jan 24, 2025

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.
But that makes sense and thanks for taking the time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants