Discussed in #26
Originally posted by DSchougaard October 21, 2022
Hi,
First off, let me thank you for the awesome program here :) It has really kick started my use of CI pipelines.
In the issues Add a "next-version" command to the CLI and Support for release candidates, we've discussed pre-release versions and came to the conclusion that the next-command was sufficient. However, after looking at implementing this in my pipelines, I see a lot of bloat in bash commands, instead of "just" letting semversioner handle it.
I can see you have branch feature/prerelease-versions where you've started the work on supporting pre-releases, but it looks like there hasn't been any activity for a bit. Is this feature still in the roadmap, or has it been abandoned, in favor for the next-release command?
Discussed in #26
Originally posted by DSchougaard October 21, 2022
Hi,
First off, let me thank you for the awesome program here :) It has really kick started my use of CI pipelines.
In the issues Add a "next-version" command to the CLI and Support for release candidates, we've discussed pre-release versions and came to the conclusion that the next-command was sufficient. However, after looking at implementing this in my pipelines, I see a lot of bloat in bash commands, instead of "just" letting semversioner handle it.
I can see you have branch feature/prerelease-versions where you've started the work on supporting pre-releases, but it looks like there hasn't been any activity for a bit. Is this feature still in the roadmap, or has it been abandoned, in favor for the next-release command?