release

You can automate semantic versioning by analyzing commit messages to determine appropriate patch, minor, or major version increments. This Skill reads version.txt, applies the version bump, and updates CHANGELOG.md to maintain release traceability.

Generating a CHANGELOG.md from commit messages involves analyzing commit history during the release process and writing updates directly into CHANGELOG.md. This ensures release records stay accurate and traceable alongside version.txt updates.

The auto option analyzes commit messages to automatically select the appropriate semantic version increment level, while manual options like patch explicitly force a specific version bump. Both update version.txt and CHANGELOG.md consistently.

Yes, version.txt is required as the Skill reads it to determine the current version before applying any bumps. It serves as the source of truth for your project's version number across multiple commits and releases.

Yes, semantic versioning release automation is designed for software projects requiring consistent version bumps across multiple commits. It analyzes the accumulated commit history since the last release to determine the appropriate version increment.

Automating version bumps from commit messages depends on consistent commit message formatting to correctly classify changes as patch, minor, or major. Without structured commit messages, the auto option may not accurately determine the appropriate increment level.