Add --bump for version command

[ischaojie]

#285

➜  o git:(main) ✗ rye version
0.1.0
➜  o git:(main) ✗ rye version 0.2.0
version set to 0.2.0
➜  o git:(main) ✗ rye version --bump major
version bumped to 1.2.0
➜  o git:(main) ✗ rye version --bump minor
version bumped to 1.3.0
➜  o git:(main) ✗ rye version --bump patch
version bumped to 1.3.1
➜  o git:(main) ✗ rye version --bump ooo

[mitsuhiko]

This makes sense, but I think it needs some reasonable story to talk about post and dev versions. Currently if you are on 1.0.0.dev0 and you bump minor you end up at 1.0.1.dev0. I propose the following logic:

• if you do a any bump and there is a dev version, remove dev: 1.0.0.dev0 -> 1.0.0 and emit a warning
• if there is a post marker on the release, remove it and bump: 1.0.0.post1 -> 1.1.0 for minor for instance

[ischaojie]

➜  o git:(main) ✗ rye version
0.1.0.dev1
➜  o git:(main) ✗ rye version --bump major
warning: dev version will be bumped to release version
version bumped to 0.1.0
➜  o git:(main) ✗ rye version             
0.1.0.post2
➜  o git:(main) ✗ rye version --bump minor
version bumped to 0.2.0

[bluss]

It would be good to give an error here on invalid input. Right now i think you could use an enum and then clap would handle it.

[ischaojie]

Thanks for the suggestion, enum is indeed in my consideration.

[mitsuhiko]

I just realized that you can have a version 1.0 which results in release being [1, 0]. This would on a minor bump cause a panic here. I think it would need to initialize missing values to 0.

[ischaojie]

➜  o git:(main) ✗ rye version
1
➜  o git:(main) ✗ rye version --bump minor
version bumped to 1.1
➜  o git:(main) ✗ rye version --bump patch
version bumped to 1.1.1
➜  o git:(main) ✗ rye version 1.0
version set to 1.0
➜  o git:(main) ✗ rye version --bump minor
version bumped to 1.1
➜  o git:(main) ✗ rye version --bump patch
version bumped to 1.1.1