Major/Minor release automations currently include a version bump such that 0.1.2a3 minor release would increment to 0.2.0 and 1.2.3a4 major release would increment to 2.0.0. OVOS (and other) packages may manually increment to 0.1.0aX, in which case a minor release would be 0.1.0.
Initial Implementation Requirements
[ ] Include an option to propose a release without incrementing versions (i.e. 0.1.0aX -> 0.1.0 OR 2.0.0aX -> 2.0.0)
Other Considerations
Something like a major release from 2.1.0aXshould release 3.0.0
Perhaps a special value for version_spec could be used to just remove alpha with no other changes to the version?
Objective
Major/Minor release automations currently include a version bump such that
0.1.2a3minor release would increment to0.2.0and1.2.3a4major release would increment to2.0.0. OVOS (and other) packages may manually increment to0.1.0aX, in which case a minor release would be0.1.0.Initial Implementation Requirements
0.1.0aX->0.1.0OR2.0.0aX -> 2.0.0)Other Considerations
2.1.0aXshould release3.0.0Perhaps a special value for
version_speccould be used to just removealphawith no other changes to the version?