Uh oh!
There was an error while loading. Please reload this page.
ci: honor breaking semver markers - #922
Merged
Merged
Conversation
alexhancock
approved these changes
Jun 23, 2026
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
This updates the SemVer Check workflow so it uses the release type implied by the PR's Conventional Commit messages. Breaking changes marked with
!or aBREAKING CHANGE:footer are checked as major releases, while unmarked changes still default to minor or patch and will fail if they introduce breaking API changes. This keeps CI aligned withrelease-plzso a real breaking change does not accidentally land with a commit message that would generate the wrong release bump as seen in the release PR #920.