harness-release

You can automate a GitHub release by running a gated workflow that coordinates version bumps, changelog promotion, PR merges, and tagging behind one confirmation. The process drafts release notes in memory and enforces a post-gate merge requirement before publishing.

Version auto-detection works by scanning project files like VERSION, package.json, pyproject.toml, or Cargo.toml to identify the target version. This detected version then coordinates the changelog promotion, tagging, and GitHub Release steps within the gated workflow.

Yes, you can use Keep a Changelog with GitHub to enforce an auditable release process. The workflow gates all release steps behind a single confirmation, ensuring version bumps, changelog promotion, and merges are repeatable and trackable before publishing.

Yes, you need the gh CLI along with Git and Python to automate PR merges and GitHub releases. These prerequisites allow the workflow to interact with GitHub APIs for merging branches, creating tags, and publishing the final release.

The best way to coordinate version bumps and tagging across teams is using an end-to-end release workflow. It auto-detects the target version from project files, drafts changes in memory, and gates the PR merge and tagging behind a single confirmation.

Gating a release workflow behind a single confirmation ensures the process is auditable and reproducible. It prevents accidental publishing by holding version bumps, changelog updates, and PR merges in memory until you explicitly approve the final release.