Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

git-cliff-release: Decide a best practice for features that should trigger a patch version bump #148

Open
janbuchar opened this issue Nov 1, 2024 · 0 comments
Open

git-cliff-release: Decide a best practice for features that should trigger a patch version bump #148

janbuchar opened this issue Nov 1, 2024 · 0 comments
Labels
t-tooling Issues with this label are in the ownership of the tooling team.

Comments

@janbuchar
Copy link
Contributor

Option 1 - introduce a new commit type (e.g., patch)

Option 2 - trigger releases with explicit release_type=patch. This requires changes to prerelease workflows - beta builds should only ever increment the patch version
@janbuchar janbuchar added the t-tooling Issues with this label are in the ownership of the tooling team. label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@janbuchar