conventional-release

To trigger the correct semantic version bump with a squash merge, write a Conventional Commit PR title using the format type(scope): summary. Selecting the correct type, such as feat or fix, determines whether semantic-release generates a patch, minor, or major release.

Yes, semantic-release works with squash merge commit messages for automated changelog generation. By configuring your repository to use the PR title as the commit message, semantic-release can parse the Conventional Commit format to automate versioning and update the changelog.

The correct Conventional Commit type for a breaking change in release-please is adding the BREAKING CHANGE footer or using the ! symbol after the type. This signals release-please to generate a major semantic version bump and document the change in the changelog.

Choose the feat commit type for github-tag-action when adding new capabilities to produce a minor bump, and use refactor when restructuring code without changing behavior to prevent an unintended release. Correct selection ensures the semantic versioning pipeline only triggers when necessary.

Yes, you can use Changesets with conventional commit PR titles. Aligning your PR titles with the type(scope): summary format ensures your default-branch release pipeline correctly interprets the changes and generates the appropriate version bump and changelog entry.

Your semantic-release pipeline skips a version bump after a squash merge because the PR title lacks a valid Conventional Commit type. Using types like chore or test, or an improperly formatted summary, signals the pipeline to suppress the release.