release-promoter

GitHub Release publication is handled by generating an annotated v-prefixed tag on the merge commit and creating the release with the changelog body. This enforces post-merge tagging discipline and returns structured results like the release URL.

Automated release tagging with changelogs works by creating an annotated v-prefixed tag on the merge commit and publishing a GitHub Release. The changelog provides the release body, enforcing post-merge discipline via sub-agent routing.

The best way to enforce post-merge tagging discipline is to use a release promotion skill that triggers sub-agent routing after a PR merges. This guarantees annotated v-prefixed tags are created and GitHub Releases are published consistently.

No, you do not need to manually create annotated tags. The automation generates the v-prefixed annotated tag directly on the merge commit and handles the GitHub Release publication automatically using the changelog body.

Yes, you can publish GitHub Releases automatically with the changelog body by running the promotion workflow after a release PR merges. The process creates the release from the generated tag and populates the release notes.

From an automated release promotion workflow, you should expect structured results containing the generated tag name and the published GitHub Release URL. This confirms successful tag creation and release publication.