Skip to content

fix: recognize breaking commit markers in releases - #5

Merged
rnwood merged 1 commit into
mainfrom
fix/conventional-commit-breaking-headers
Nov 1, 2026
Merged

rnwood merged 1 commit into
mainfrom
fix/conventional-commit-breaking-headers

Conversation

Copilot AI commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Use the Conventional Commits preset for release analysis and generated release notes, so ! headers trigger major releases and appear as breaking changes.
  • Pin the compatible conventional-changelog-conventionalcommits preset dependency.

Validation

  • Verified feat!: is classified as a major release.
  • Verified generated release notes include the breaking-change section.
  • npm ls --depth=0, JSON validation, and git diff --check passed.

Configure semantic-release commit analysis and generated notes with the Conventional Commits preset, and lock the compatible preset package.

Co-authored-by: Copilot <[email protected]>
@rnwood
rnwood marked this pull request as ready for review November 1, 2026 10:17
@rnwood
rnwood merged commit 66a8da5 into main Nov 1, 2026
1 check passed
@rnwood
rnwood deleted the fix/conventional-commit-breaking-headers branch November 1, 2026 10:17
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.

2 participants