crelease

Automate semantic version bumping by identifying the appropriate version increment from specs merged since the last git tag, then generate a changelog entry and update the version file accordingly to ensure consistent releases.

Creating annotated git tags automatically involves deriving release notes from merged specs, applying pre-tag sanity checks, and producing a release tag with an annotated message to ensure auditable versioning without manual guesswork.

Generating a changelog entry from merged specs involves analyzing spec changes since the last tag to derive the next version bump, then compiling those spec details into release notes for the changelog before finalizing the git tag.

Yes, you can optionally push the created git tag and release to the remote repository automatically after confirming the version bump, changelog generation, and version file updates have been applied successfully.

Automated release tagging requires manual confirmation before proceeding, ensuring the user reviews the derived version bump applied to selected specs and the generated changelog entry before the final git tag is created.

Deriving version bumps from merged specs requires existing specs and a previous git tag to function correctly, and it relies on spec content to determine the appropriate version increment rather than parsing arbitrary commit messages.