-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
Incorrect PEP440 pre-release version handling #1119
Comments
The bump for tag+1 intend The mission prerelease in the tuple is a bug |
Ah, that is intended, I see. I misunderstood. I can adjust my workflow to that. But, if I wanted to, can I turn that off? So that only dev* part is incremented? Weird default though. What if I want my next version to be a different kind of pre-release, like beta? And I never intend to create a tag with the version setuptools-scm thought will come to be. Solution: Use version_scheme |
A tag with .dev at the end tells it the start of a new line |
…er-full-version fixes #1119: consider all version parts for version tuple
reopened due to yank |
Issue 1
No pre-release in version tuple. Contents of the version file generated from tag v1.0.0a1 (HEAD is at tag):
Issue 2
Arbitrary pre-release version bump with HEAD at tag + 1. Should remain a1 not bumped to a2. Issue 1 persists as well. "modif" commit is just a string update to a print function call.
I experienced these using hatch-vcs, I was able reproduce using setuptools-scm directly.
Reproducing
Then edit the pyproject so setuptools-scm is set up.
Then commit and tag as shown above. I used uv, so building is
uv build
.Issue 1 build output - at tag
Issue 2 build output - at tag +1
The text was updated successfully, but these errors were encountered: