fix(release): use conventionalcommits preset#74
Merged
Conversation
The angular preset (default) does not recognize the `!` breaking change indicator in commit subjects like `feat!:`. Switch to the conventionalcommits preset which supports both `!` and `BREAKING CHANGE:` footer. BREAKING CHANGE: Illumina sample sheet V2 API was redesigned in the previous commit for NovaSeq X and cloud support
spawnia
approved these changes
Feb 27, 2026
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.
Summary
angularpreset toconventionalcommitsconventional-changelog-conventionalcommitsdependencyBREAKING CHANGEfooter to trigger the v6.0.0 release that was missed by thefeat(samplesheet)!commit in feat(samplesheet)!: Update Illumina sample sheets for NovaSeq X and cloud support #72Why
The
angularpreset does not recognize the!breaking change indicator in commit subjects (e.g.,feat!:). It only looks forBREAKING CHANGE:in the commit footer. Theconventionalcommitspreset supports both, which matches what the project documents in CLAUDE.md.This caused the release workflow to skip releasing after #72 merged.
Test plan
v6.0.0with the breaking change from feat(samplesheet)!: Update Illumina sample sheets for NovaSeq X and cloud support #72 included in the changelog