chore: add allow_zero_version to pyproject.toml in response to semant… #206
Conversation
This file contains hidden or 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
…ic release breaking change Signed-off-by: Evan Spearman <[email protected]>
|
AWS-Samuel
approved these changes
Jun 16, 2025
mwiebe
approved these changes
Jun 16, 2025
Contributor
|
Fixed in #209 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What was the problem/requirement? (What/Why)
Semantic release broke a default setting so it would force our project to go version 1.0.0.
What was the solution? (How)
Add a flag in the pyproject.toml to re-enable zero versions.
What is the impact of this change?
Gets back to our version structure
How was this change tested?
N/A
Was this change documented?
No.
Is this a breaking change?
No.