Prerelease Version Labels

[darthtrevino]

Hey @kekyo , I love your project!

One thing I'd like to be able to do is have prerelease version labels between git tags. For example, if I'm two commits after a release 1.2.1 on main, I'd hope to see something like 1.2.1-prerelease-<commit-hash>. I'd like to cut pre-release versions automatically without adjusting the semver triad.

Once I cut a release tag, say v1.3.0, and my git HEAD is at that tag, I'd expect the tool to just use the raw version (1.3.0)

Is this possible with the current rulesets, or would this involve featur dev?

[kekyo]

Thank you for using RelaxVersioner!

That rule would not be possible in the current version. However, I am interested in adding the feature.

For example, if we move two commits forward from a commit tagged 1.2.1 and apply 1.2.1-release-, would this be applied to the AssemblyInformationalVersion?

Would the assembly version become 1.2.3?
Or would it remain 1.2.1?

If the former, it seems achievable by considering a special formatting scheme. If the latter, we might need some kind of flag to explicitly indicate this formatting (which might be specified in a PropertyGroup).

[darthtrevino]

Hey @kekyo ,
I believe that poetry-dynamic-versioning will let you customize this behavior, although the non-bumped approach is the default. Between these two options, I think the first makes the most sense, and the new release would be v1.2.1.post2

1. No Bump (poetry-dynamic-versioning default)

gitGraph
   commit id: "v1.2.1" tag: "v1.2.1"
   commit id: "v1.2.1.post.1"
   commit id: "v1.2.1.post.2"

Loading

2. Bump

gitGraph
   commit id: "v1.2.1" tag: "v1.2.1"
   commit id: "v1.2.2.pre.1"
   commit id: "v1.2.2.pre.2"

Loading