Support prerelease

[dumptruckman]

PR Notes

• Reviewed Checks: Verified output of Integration Tests
• Have set labels for release level

I did not run integration tests locally as they did not work. Unsure how to get them to run. This could use some documentation but I wanted to get a feel for your thoughts on it. I suspect this hasn't been supported yet due there being no standard definition of prerelease versioning that can be followed. This PR takes an opinionated approach using 1.0.0 -> 1.0.0-pre -> 1.0.0-pre.1 -> 1.0.0-pre.2 etc. It also bumps the main version separately so the PR labels can be combined to bump both at the same time.

Fixes #76.

[dumptruckman]

After testing this in action a little bit it seems that there's still some work to be done. Getting from an existing prerelease version like 4.2.1-pre to 4.2.1-pre.1 is not working yet.

[dumptruckman]

Well, I got this working how we're trying to use it. I think maybe the release it fetches should be based on whether it's doing a prerelease or not though. It would be nice to have it do a full change log to the last non-prerelease version when doing a non-prerelease release.

[hermanbanken]

Would be cool if this was added 😄

[Kripu77]

Would be cool if this was added 😄

@rymndhng would be great if this could be added to the project.

[Kripu77]

PR Notes

• Reviewed Checks: Verified output of Integration Tests
• Have set labels for release level

I did not run integration tests locally as they did not work. Unsure how to get them to run. This could use some documentation but I wanted to get a feel for your thoughts on it. I suspect this hasn't been supported yet due there being no standard definition of prerelease versioning that can be followed. This PR takes an opinionated approach using 1.0.0 -> 1.0.0-pre -> 1.0.0-pre.1 -> 1.0.0-pre.2 etc. It also bumps the main version separately so the PR labels can be combined to bump both at the same time.

Fixes #76.

Hey mate, based on SemVer principles would you consider adding generic pre-labels for example:

• alhpa
• beta
• rc

And, let the user decide the pre-release label based on the labels attached with the PR?

[afgarcia86]

Any reason this can't be merged?

[Kripu77]

@afgarcia86
Seems like this repo isn't being maintained anymore.

[afgarcia86]

Yea I ended up going with ***@***.*** that doesn’t do the tagging and release but has the dynamic versioning I needed. Best Regards, Andres Garcia Software Engineer <http://www.andresthegiant.com>http://www.andresthegiant.com 703.389.1081

…

On Wed, Sep 4, 2024 at 8:58 PM Kripu Khadka ***@***.***> wrote: @afgarcia86 <https://github.com/afgarcia86> Seems like this repo isn't being maintained anymore. — Reply to this email directly, view it on GitHub <#83 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA3QMJN3DKESDM2KW23FKMTZU6UCPAVCNFSM6AAAAAAVG5ZFIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGM4TMOJTGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>