feat(version): add MANUAL_VERSION, --next and --patch to version comm… #1724
Conversation
…and, remove type alias
bearomorphism
requested review from
Lee-W,
noirbizarre and
woile
as code owners
github-actions
bot
added
pr-status: wait-for-review
type: feature
|
@Lee-W I already ran Do you have any ideas why this happen |
| version = f"{version_scheme.minor}" | ||
| out.write(version.major) | ||
| return | ||
| if self.arguments.get("minor"): |
There was a problem hiding this comment.
I realize now that this creates problems with the (not)monotonic kind of versions (and possible non-semver). I'm not sure what to do about it.
I think for now it's fine that if you diverge too much from semver in your custom version scheme, then you won't get the full range of features.
|
There was a way to run all the pre-commits, but I don't remember how it works 😅 |
|
|
||
|
|
||
| @pytest.mark.parametrize( | ||
| "next_version, current_version, expected_version", |
There was a problem hiding this comment.
maybe rename next_version to next_increment?
In the user facing cli, it makes sense semantically: --next=MAJOR (give me the next major).
| assert expected_version in captured.out | ||
|
|
||
|
|
||
| def test_next_version_invalid_version(config, capsys): |
There was a problem hiding this comment.
what about having a parametrize of the combinations that should fail:
@pytest.mark.parametrize(
"args",
[
# incomplete list:
{"next"},
# ...
{"--verbose", "next"}
]
)
| out.error("Invalid version.") | ||
| return | ||
|
|
||
| if next_str := self.arguments.get("next"): |
There was a problem hiding this comment.
what would happen here if I run cz version --project --next? I would expect that to work
|
Nice to see this going forward 🎉 |
2 participants
…and, remove type alias
Closes #1678, #1679
Manually tested and added test cases, the result LGTM.