Skip to content

chore: Allow zero version when releasing#249

Merged
miabatta merged 1 commit intoOpenJobDescription:mainlinefrom
miabatta:mainline
Jun 24, 2025
Merged

chore: Allow zero version when releasing#249
miabatta merged 1 commit intoOpenJobDescription:mainlinefrom
miabatta:mainline

Conversation

@miabatta
Copy link
Contributor

What was the problem/requirement? (What/Why)

Project major version is automatically bumped when releasing

What was the solution? (How)

Add allow_zero_version = true to semantic release settings

What is the impact of this change?

No unwanted major version bump :)

How was this change tested?

n/a, project configuration change

See DEVELOPMENT.md for information on running tests.

  • Have you run the unit tests?
    Yes just in case

Was this change documented?

n/a

Is this a breaking change?

definitely not

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.

Signed-off-by: Mia Battad <133708990+miabatta@users.noreply.github.com>
@miabatta miabatta requested a review from a team as a code owner June 24, 2025 18:14
@sonarqubecloud
Copy link

@miabatta miabatta enabled auto-merge (rebase) June 24, 2025 18:24
@miabatta miabatta merged commit 165ff71 into OpenJobDescription:mainline Jun 24, 2025
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants