release-please VS conventional-changelog

Conventional Commits

We've covered everything about writing well-formatted and structured code without worrying too much about it anymore. The only part we haven't explored yet is linting commit messages. Commitlint will help us here. It allows you to configure any rules you want for the commit message, but we're going to use the Conventional Commits specification, one of the most popular conventions you'll find.

Commit Management with Conventional Commits: The Conventional Commits methodology is adopted to maintain a clear and structured record of changes with the help of commitlint.

Validate if the commit titles adhere to the Conventional Commits Specification in Merge requests.

Check out https://www.conventionalcommits.org

FYI there is already a popular tool that does just this with a very similar name: https://github.com/googleapis/release-please

The feature commit should have a clear defined message - Don't re-invent here - There exists a fairly used and accepted convention called Conventional Commits, so we are going to use that.

Check out https://github.com/googleapis/release-please

conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.

Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog

Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.

I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.

conventional-changelog-conventionalcommits

[1] - https://github.com/conventional-changelog/conventional-chang...

I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.

@semantic-release/commit-analyzer It determines the type of our release (e.g. major, minor, patch) by analyzing commits with conventional-changelog. semantic-release uses Angular Commit Message Conventions by default.