xerahs-release-bump-tag

Automated release sequencing orchestrates end-to-end git workflows by verifying builds, bumping versions, committing changes, pushing, and creating semantic tags. It reduces manual toil and ensures build success before tagging and releasing across CI pipelines.

The release workflow performs maintenance chores, updates the changelog, verifies the build, bumps the version, commits, pushes, and creates a tag. It then monitors the GitHub Actions release workflow every 2 minutes until completion.

Yes, the release automation satisfies guardrails for version synchronization across Directory.Build.props files. It ensures version numbers are consistently updated before committing changes and pushing the semantic tag.

When the monitored GitHub Actions release workflow fails, the sequence inspects logs, fixes the root cause, and retries the process with the next patch version. This retry logic ensures safe release sequencing without manual intervention.

Yes, you can optionally mark the release as a prerelease during the sequence. After build verification, version bumping, and tag creation, the workflow supports optional prerelease marking to manage pre-production distributions.

The release sequence automatically performs maintenance chores by running git pull --recurse-submodules and git submodule update --init --recursive. This ensures all submodules are properly initialized before build verification and tagging.