fledge

fledge copied to clipboard

pre_release() should be smart about version numbers

5

0.x.99.9yyy -> 0.(x+1).0 x.99.99.9yyy -> (x+1).0.0 We also might want new modes for `bump_version()`: `"pre-minor"` -> x.y.99.9000, `"pre-major"` -> `x.99.99.9000` This is likely a duplicate.

krlmlr

Print version number in a nicer way

1

In ``` ✔ Package version bumped to 0.1.0.9003. ``` could the components major-minor-patch-dev be more different?

maelle

feat: add which "pre-minor" and "pre-major" to update_version()

3

Fix #413 Part of #401 As you will see there are two questions in the comments ```r # first check there is a fourth component, if not # the which...

maelle

Showing when one goes to pre-minor for instance. Related to #401 #413

maelle

What if someone uses --- several times in a commit message

4

should there be some sort of warning

maelle

Via https://github.com/cynkra/fledge/issues/341#issuecomment-1133813262 It could at least be a standard _inside fledge_.

maelle

Use conventional commit to suggest a which for bump_version()

2

Related to #341 > If we keep that automated use case in mind during development -- my vision is that bumping the "dev" version would use "pre-minor" or "pre-major" if...

maelle

Via #401 > We also might want new modes for bump_version(): "pre-minor" -> x.y.99.9000, "pre-major" -> x.99.99.9000

maelle

Fix #361

maelle

Include reference to issue closed with a PR?

3

https://github.com/cynkra/dm/commit/d1ab1fcb5bca29b145375b3c98c20355ab09e248

krlmlr