create-release

Automate semantic versioning and changelog generation by managing version bumps in Directory.Build.props and drafting changelog entries from commit history. This ensures version consistency across Git tags and project files during Gitflow release branch creation.

Creating a release branch and opening a pull request is handled by executing GitHub CLI commands to branch from develop, bump versions, and automatically target the main branch for review. This streamlines Gitflow release and hotfix workflows.

Yes, a clean working tree is required before starting an automated software release. The process includes robust pre-checks for branch existence, version consistency, and working tree cleanliness to prevent committing uncommitted changes into release branches.

Yes, you can generate draft changelog entries from commit history following the Keep a Changelog format. The automation parses previous commits to populate the release notes accurately when creating release or hotfix branches.

Hotfix branches differ from release branches by targeting emergency fixes directly from the main branch, while release branches originate from develop. Both automate version bumps, changelog updates, and pull request creation targeting main.

Version consistency between Git tags and project files matters because mismatched versions cause deployment failures and confuse dependency resolution. The release process performs robust checks to ensure Directory.Build.props matches the intended semantic versioning tag.