chore: Allow zero version for Semantic Release#209
Merged
miabatta merged 1 commit intoOpenJobDescription:mainlinefrom Jun 30, 2025
Merged
chore: Allow zero version for Semantic Release#209miabatta merged 1 commit intoOpenJobDescription:mainlinefrom
miabatta merged 1 commit intoOpenJobDescription:mainlinefrom
Conversation
Signed-off-by: Mia Battad <133708990+miabatta@users.noreply.github.com>
|
edwards-aws
approved these changes
Jun 30, 2025
jericht
approved these changes
Jun 30, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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)
Bump actions automatically go to 1.0.0 due to a change in Semantic Release.
What was the solution? (How)
Add a flag to
pyproject.tomlto retain 0 version.What is the impact of this change?
No unwanted version bumps :)
How was this change tested?
n/a
See DEVELOPMENT.md for information on running tests.
Yes just for thoroughness
Was this change documented?
n/a
Is this a breaking change?
nop
Does this change impact security?
nop
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.