release

Automate semantic versioning by calculating the next version directly from conventional commit history, updating the CHANGELOG.md with grouped commits, and tagging the repository. This workflow ensures consistent version bumping without manual calculation.

Yes, you can override the calculated semver version during a git release by providing an explicit --version override. The workflow will use the specified version to update the CHANGELOG and create the git tag instead of deriving it from commit history.

The release workflow optionally creates a GitHub release via the gh CLI when a token is present. If the tooling is missing, it gracefully skips release creation while still completing the semver tag and CHANGELOG updates locally.

The release workflow validates git history depth and ensures a clean working tree before proceeding. If the working tree is not clean, the process will halt to prevent tagging uncommitted changes and ensure a stable release artifact.

Generate an auditable release summary by running the automated release workflow, which emits a durable release-summary.md file. This artifact records the version, commits, tags, release status, and any skipped steps for full traceability.

The best way to automate changelog generation and git tagging is using a single workflow that parses conventional commits to determine semver, appends a new version section to CHANGELOG.md, and creates the corresponding git tag automatically.