release

Automating semantic versioning and CHANGELOG updates involves bumping the version number and moving entries from the Unreleased section to the new version section. This Skill handles that automatically while also regenerating documentation and committing the release tag.

The best way to create a versioned release with documentation regeneration is to use an automated workflow that determines the semantic version, updates the CHANGELOG, refreshes docs, and commits the tag in one step. This Skill executes that entire process.

Semantic version bumping with an existing CHANGELOG.md works by applying versioning rules to increment the number and migrating Unreleased entries to a newly created version section. This ensures the CHANGELOG accurately reflects the new release.

Yes, you can specify a custom version number instead of a semantic versioning keyword. By passing the desired version directly, the automation will apply that exact number to the version bump, CHANGELOG update, and tagging process.

No, you do not need to manually commit and tag your project after updating the CHANGELOG. The release automation handles the commit and tagging automatically once the version bump and documentation regeneration are complete.

You should use release automation for version control management when your project workflows require consistent versioning, accurate CHANGELOG updates, and synchronized documentation regeneration without manual intervention.