paw-tools-release

To automate GitHub releases, you use a workflow that bumps versions, generates changelogs, creates git tags, and drafts GitHub releases. It requires a Git repository, gh CLI authentication, and a clean working tree.

End-to-end release automation orchestrates the entire publishing process by performing version bumps, generating changelogs, tagging commits in Git, and creating final GitHub releases. This ensures consistent and auditable software releases across multiple repositories.

Yes, you need the gh CLI authenticated to automate git tagging and version bumps, along with a Git repository and a clean working tree. The automation validates these prerequisites and reports actionable remediation steps if missing.

Yes, you can run automated release workflows headless without user interaction. The automation supports both headless non-interactive workflows for continuous integration and interactive workflows for manual execution.

To create pre-release versions, you use configurable release branches with optional pre-release flags during the automation workflow. This allows you to target specific branches and designate the release as a pre-release when drafting the GitHub release.

Your automated release fails with a dirty working tree because the automation requires a clean working tree to ensure auditable releases. You must commit or stash uncommitted changes before initiating the version bump and tagging process.