Skip to content

ci: support major/minor release bumps via PR title convention - #135

Merged
mikemadeja merged 1 commit into
developfrom
ci/major-minor-release-convention
Oct 2, 2026
Merged

mikemadeja merged 1 commit into
developfrom
ci/major-minor-release-convention

Conversation

@mikemadeja

Copy link
Copy Markdown
Owner

Summary

  • The auto-release workflow (CreateRelease.yml) always bumped only the patch version on every develop->main merge, with no way to cut a major or minor release
  • Including "major release" or "minor release" (case-insensitive, anywhere in the title) in the develop->main PR's title now bumps that version component instead and resets the components below it to 0 - e.g. a PR titled "Major release: v1.0.0" against the current v0.0.40 tag produces v1.0.0
  • Titles without either phrase keep the existing patch-bump behavior, so this is fully backward compatible

Test plan

  • Verified the bump logic in isolation with sample PR titles (Major release: ... -> major bump, Minor Release: ... -> minor bump, ordinary titles -> patch bump as before)
  • YAML parses correctly
  • N/A - can't run the actual GitHub Actions workflow outside of a real PR merge event; this will be exercised for real the next time a develop->main PR titled "major release"/"minor release" merges

🤖 Generated with Claude Code

The auto-release workflow always bumped the patch version on every
develop->main merge, with no way to cut a major or minor release.
Including "major release" or "minor release" (case-insensitive) in
the PR's title now bumps that version component instead, resetting
the components below it to 0. Titles without either phrase keep the
existing patch-bump behavior.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
@mikemadeja
mikemadeja merged commit 76bad22 into develop Oct 2, 2026
3 checks passed
@mikemadeja mikemadeja mentioned this pull request Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant