release

Automating Git version bumping and GitHub release publishing is handled by a script-driven workflow that bumps versions, creates annotated tags, and publishes draft releases directly to GitHub.

Creating beta releases from a develop branch and stable releases from main requires a pipeline that infers the target version based on the current branch, creates the matching annotated Git tag, and generates automated release notes.

Waiting for CI pipeline builds before creating a new Git tag is supported, allowing the release pipeline to pause for ongoing GitHub workflow runs to complete before publishing the final draft release.

Generating automated release notes for a GitHub draft release is integrated into the version bumping workflow, which applies script-driven logic to interact with the GitHub CLI and populate the release details.

The release automation pipeline requires the Git and GitHub CLI tools to be present in the environment, as it relies on these external scripts to validate inputs, create annotated tags, and enforce the overall release workflow.

Using a script-driven workflow for versioning instead of manual Git tagging reduces human error by automatically validating inputs, bumping versions consistently, and orchestrating the transition from develop to main through annotated tags.