full-release

A full git release workflow automates changelog updates, version bumps, tag creation, CI monitoring, and distribution sync. This skill orchestrates that end-to-end process, requiring explicit confirmation before pushing tags to ensure safe publication.

Yes, the release workflow supports preview versions. It automatically skips preview-incompatible publishing steps, such as Homebrew tap updates and website documentation syncs, when releasing alpha, beta, or rc versions.

Yes, you can sync Homebrew taps and deploy website documentation during a GitHub release. The workflow coordinates these distribution channel updates alongside milestone stamping and CI verification.

To safely gate git tag creation, the workflow requires explicit user confirmation before pushing the tag. This safety mechanism prevents accidental publication before the release commit and build verification are finalized.

The best way to coordinate CI monitoring and release verification is through an orchestrated workflow that watches CI pipelines and verifies the GitHub release automatically after tag creation.

Milestone stamping during a software release workflow couples release notes with milestone management. The workflow applies this stamping as part of the release coordination phase following tag creation and CI verification.