Move from setuptools_scm to setuptools-git-versioning #91
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
setuptools has recently deprecated legacy versioning, so we moved to configuring setuptools_scm with the no-guess-dev option. It appears that a release always adds version bump in addition to the git tag. e.g. release 1.0.1 reports its version as 1.0.1.post1.dev0+g3859438.d20230308 while 3859438 is the commit that was tagged on master as 1.0.1, the version has a post-release suffix (and appears to have been interpreted as a dev release?). The issue reported here appears to be the same: pypa/setuptools-scm#812 Trying setuptools-git-versioning instead in the hope that it is less "clever".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
setuptools has recently deprecated legacy versioning, so we moved to configuring setuptools_scm with the no-guess-dev option. It appears that a release always adds version bump in addition to the git tag.
e.g. release 1.0.1 reports its version as
1.0.1.post1.dev0+g3859438.d20230308
while 3859438 is the commit that was tagged on master as 1.0.1, the version has a post-release suffix (and appears to have been interpreted as a dev release?).
The issue reported here appears to be the same:
pypa/setuptools-scm#812
Trying setuptools-git-versioning instead in the hope that it is less "clever".