fix(release): keep the latest alias on the highest version when a hotfix ships - #1262
Merged
Merged
Conversation
BryanFRD
enabled auto-merge (squash)
October 3, 2026 10:55
![ferrfleet[bot]](https://avatars.githubusercontent.com/in/4354888?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Looks correct. latest_moves reuses backward_from, so the alias stays put on an older-line release, still moves with --force, and still moves when the existing tag message isn't one FerrFlow wrote. Skipping the alias with a status line instead of an error is the right call, because a hotfix shouldn't fail the release. Both tests cover the skip path and the force path, and the EN/FR docs match.
Nit: the pkg_outputs.iter_mut().rev().find(...) lookup is now duplicated in move_floating_tag and latest_moves. A small push_line(plan, pkg, line) helper would remove the copy.
Test and Coverage were still running when I reviewed, so I haven't seen them pass.
ferrflow Bot
added a commit
that referenced
this pull request
Oct 3, 2026
## [7.27.3] - 2026-10-03 ### Bug Fixes - fix(release): keep the latest alias on the highest version when a hotfix ships (#1262)
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.
Closes #1232
Releasing 1.2.4 after 2.0.0 moved
latestTagto 1.2.4. Following the decision on the issue,latestnow means the highest released version, like the major and minor floating tags since #1226.The behaviour differs from those tags on one point: a backward
latestdoes not fail the release. A hotfix on a maintenance line is routine, and failing it would force--force, which would then draglatestbackward, the very thing being prevented. So the release goes through,lateststays where it is, and the package output saysKept latest on 2.0.0: 1.2.4 is older.--forcestill moves it backward, with a warning, for anyone who wants the old behaviour.This changes what users who relied on "most recently released" see, which is why the issue asked for a decision first. The config docs (EN and FR) said
latestTagwas exempt from the guard; they now describe the new rule.Tests: a hotfix leaves
latestand its remote ref alone whilev1still follows;--forcemoves it back. The first fails without the fix.