release-to-main

Automating a dev-to-main release requires assessing branch divergence, rebasing dev onto main, calculating the semantic version bump from conventional commits, and publishing a GitHub release. This workflow prevents manual errors and ensures branch synchronization.

Calculating semantic versions from conventional commits involves parsing commit messages to determine the version bump. This Skill automates semantic version calculation and prompts for user confirmation before tagging and releasing.

Yes, you need the GitHub CLI (gh) installed and authenticated to publish releases. This Skill uses the Git CLI for local branch operations and the GitHub CLI to create GitHub tags and releases remotely.

A dev-to-main rebase workflow handles divergence by assessing the branches before merging. This Skill includes divergence guards to ensure a safe merge and performs a post-release sync to rebase dev onto the updated main branch.

Yes, GitHub release publishing can be automated with validated notes. This Skill creates Git tags and publishes GitHub releases, ensuring release notes are properly validated during the automated dev-to-main merge process.

You should not use an automated Git branch merge if your repository lacks separate dev and main branches or does not follow conventional commit standards. This Skill requires a specific remote Git repository structure to function correctly.