ci: deterministic v3.6.x release versioning#51
Closed
lacraig2 wants to merge 1 commit into
Closed
Conversation
The merge-to-main release produced v3.3.11 -- reecetech/version-increment mis-derived the base from the legacy v3.5.x-beta tags (a regression vs the old beta line). Replace it with a deterministic step that continues the v3.6.x line: next = highest existing v3.6.* patch + 1, or v3.6.1 when none exist. Monotonic and predictable; bump MAJOR_MINOR to start a new minor later.
Contributor
Author
|
Closing in favor of the simpler approach: version-increment reads tags and ignores the -beta semver prereleases, so it bumped from the highest non-prerelease tag (v3.3.10 → v3.3.11). Pushing a bare v3.6.0 tag makes that the base → next release is v3.6.1, then forward. No workflow change needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The first merge-to-main release published v3.3.11 —
reecetech/version-incrementmis-derived the base from the legacyv3.5.x-betatag history, producing a version lower than the priorv3.5.33-beta.Fix
Replace version-increment with a deterministic step in the
aggregatejob: the next version continues the v3.6.x line —next = highest existing v3.6.* patch + 1, or v3.6.1 when none exist. Monotonic and predictable. To start a new minor line later, bumpMAJOR_MINOR.push;dev_*→ prerelease).Verified the logic locally against live tags → computes
v3.6.1.