release

To automate git release versioning and changelog generation, you can use a workflow that auto-detects version changes from conventional commits, applies semver rules, updates your configuration file, and generates CHANGELOG.md automatically.

Creating a git tag and pushing it to origin during a release involves performing pre-release checks, updating configuration files, committing changes, creating the tag, and pushing everything to origin to trigger optional CI publishing actions.

Yes, you can explicitly specify a version number instead of using auto-detection from commits, allowing you to override the automatic semver bumping and directly input the desired version for validation and publishing.

The release workflow validates semver rules and checks for existing tags to ensure version integrity, preventing duplicate tags and ensuring the proposed version number strictly follows semantic versioning standards before committing.

The best way to update moe-bangumi.cabal and publish builds in a single release is using an end-to-end automation workflow that updates the configuration, commits changes, creates git tags, pushes to origin, and coordinates with CI actions to publish artifacts.

When using conventional commits for auto-detecting release versions, limitations include the reliance on strict commit message formatting; if messages deviate from conventions, the semver auto-detection may fail or require explicit version input instead.