Skip to content

fix(release): assign the next prerelease number - #1443

Merged
coreybutler merged 1 commit into
mainfrom
fix/auto-prerelease-number
Oct 12, 2026
Merged

coreybutler merged 1 commit into
mainfrom
fix/auto-prerelease-number

Conversation

@coreybutler

Copy link
Copy Markdown
Collaborator

Summary

  • The Community Release form calls the dropdown Release Type and uses General for a normal manifest release.
  • Alpha, beta, rc, and hotfix numbers are taken from the next unused GitHub tag. The form no longer asks for a number.
  • Hotfix Mainline names the general release the hotfix patches. An empty value uses the latest general release.

Test plan

  • Run Release Community Build from this branch with Release Type General and confirm the version is the manifest version.
  • Run with Release Type beta and confirm the tag is the next beta, currently v2.0.2-beta.4.
  • Run with Release Type hotfix and Hotfix Mainline 2.0.1 and confirm the tag is the next hotfix, currently v2.0.1-hotfix.3.
  • Leave Hotfix Mainline empty on a hotfix run and confirm the base is the latest general release.

The release form no longer asks for a number. General publishes the manifest version, and a hotfix uses the Hotfix Mainline.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coreybutler
coreybutler merged commit 80ac750 into main Oct 12, 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