This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
chore: prevent normalization of semver 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
product-auto-label
bot
added
the
api: bigqueryreservation
google-cla
bot
added
the
cla: yes
tswast
approved these changes
Apr 15, 2021
tswast
pushed a commit
that referenced
this pull request
Apr 21, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When there is a patch version added to semver versioning, setuptools.setup(version) will normalize the versioning from
-patchto.patchwhich is not correct SEMVER versioning. The added feature with setuptools.sic(version) will prevent this from happening.