publish-release

An end-to-end git release workflow is automated by coordinating maintenance, changelog generation, build verification, version bumping, tag creation, and release monitoring into a single repeatable script. Pre-checks enforce that the build passes before bumping versions.

Yes, monitoring a GitHub Actions release workflow is handled by continuously polling the status every 2 minutes after the git commit and tag are pushed. It logs and retries on failure, ensuring the release pipeline completes successfully.

Prerelease handling is supported and defaults to enabled unless explicitly opted out. The workflow enforces guardrails to ensure standard release notes are present before proceeding with the version bump and tag creation.

Running this strict release pipeline requires git, gh, awk, grep, sort, mktemp, and tr installed in the environment. These tools coordinate the version file updates, changelog parsing, and tag operations.

Updating all tracked version files is executed automatically during the version bump phase. The workflow enforces pre-checks before the bump and updates every tracked file before pushing the commit and creating the git tag.

A strict end-to-end release flow reduces manual errors and ensures traceability by enforcing guardrails like build verification before bumping. It orchestrates maintenance, changelog updates, and monitoring reliably for CI/CD pipelines.