[conductor] Not auto-incrementing new betas #107860
Description
I tried to cut a new beta release with:
./dev/conductor/bin/conductor start \
--candidate-branch=flutter-3.2-candidate.5 \
--release-channel=beta \
[email protected]:caseyhillers/flutter.git \
[email protected]:caseyhillers/engine.git \
--dart-revision=e020f8158a4ad7bae2584f5789fddd927022eb07 \
However, Conductor had some issues picking up the new version.
Repository framework is checked out at revision "08457a3d7ef81cec0662bce6f6ed6db37b6d9b8c".
Parsed version 3.0.0-0.0.pre.1600 has a different y value than candidate branch flutter-3.2-candidate.5
About to tag the release candidate branch branchpoint of 08457a3d7ef81cec0662bce6f6ed6db37b6d9b8c as 3.2.0-5.0.pre and push it to [email protected]:flutter/flutter.git. Is this correct? (y/n) n
My expectation is that the conductor would've realize the candidate branch has changed, and it can increment Y to create 3.3.0-0.0.pre as the release version.
As a workaround, I added --version-override with the expected values.