fix: force major version bump#1041
Merged
Merged
Conversation
bmtcril
approved these changes
Mar 24, 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
2 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.
A note on this - the current code for github-tag-action does not support conventionalcommit analyzer (only angular) so our commit messages are not interpreted correctly which means using the 'bump version' action in GitHub only bumps minor releases, not major.
There is a PR that will change this, but it needs to be merged/compiled into the workplace action before we can use it.
So for now, we will force the action to do a major version bump, and hope that the PR gets reviewed soon so we can remove this line and instead specify
commit_analyzer_preset: conventionalcommit