semantic-release automates release-note generation and version updates by examining structured commit history. It requires commit messages in the format its analyzer can parse, making descriptive commits operationally important. section 5.3
Use it after packaging a module to summarize breaking changes and communicate updates to other teams. Keep the resulting release notes in a repository document such as a changelog, and retain version-control tags so artifacts remain traceable to code. section 5.3
Structured commit drives a major version
A commit such as “feat(security): store password in secrets manager” can be analyzed as a major feature, causing the automated release tool to update the tag to v2.0.0. section 5.3
