release

Automate semantic versioning by analyzing conventional commit messages to detect major, minor, or patch version bumps, then automatically generate or update your CHANGELOG.md file. This eliminates manual version tracking and changelog editing during software releases.

Automate Git tagging and GitHub release creation by using Git and GitHub CLI to execute commits, apply version tags, push to remote repositories, and publish releases with attached provider assets. This ensures consistent release workflows without manual repository interaction.

Yes, you need Git, GitHub CLI (gh), and yamllint installed to automate your software release workflow. These dependencies are required for version validation, remote repository pushing, and creating GitHub releases with provider assets.

Yes, you can preview a version bump and changelog update using the dry-run mode. This allows you to verify all automated release actions, including commit creation and tagging, before any changes are executed or pushed to your remote repository.

Conventional commit based version detection works by parsing your Git commit history to identify specific commit types. It uses these structured commit messages to automatically determine whether the next release requires a major, minor, or patch version bump.

Using conventional commits for automated version detection requires strict adherence to the conventional commit message format. If your project history contains non-compliant commit messages, the automated version bump calculation and subsequent changelog generation may not accurately reflect the actual changes.