release

Automate GitHub releases by wrapping uncommitted changes, bumping versions, monitoring CI on the main branch, and creating a release page if CI passes. You can trigger this by providing explicit instructions with a specific version number or SemVer term like 'patch'.

Ensure a clean repository commit before a version release by using commit wrapping, which automatically bundles any uncommitted changes into a single commit. This prepares the repository for a clean and automated version bump and deployment process.

Yes, release automation works directly with GitHub Actions for CI workflows. The process watches the CI run on the main branch and creates an annotated tag only if the CI checks pass, ensuring that releases are built on validated code.

Yes, you can use SemVer terms to trigger repository release automation. By providing explicit instructions like 'release patch' or 'release minor', the automation determines and applies the correct version bump automatically.

Create a GitHub Release page automatically after passing CI checks by pushing an annotated tag once the main branch CI is green. The release automation then generates the GitHub Release page with all necessary information.