-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support passing argument to toggle between stable and pre-release release notes #597
Comments
@AdmiringWorm this sounds like the correct path forward. Were you wanting to take a stab at this? |
Yeah, most likely, either during the weekend or sometime next week. |
@AdmiringWorm makes sense! Thanks |
I have started looking into this request now. |
…ase notes This allows an argument called 'create-pre-release' to be used when calling the cake build script for specifically setting the milestone to the generated SemVer version, instead of a stable version. On tagged releases this should always be the SemVer version no matter what is used.
…ase notes This allows an argument called 'create-pre-release' to be used when calling the cake build script for specifically setting the milestone to the generated SemVer version, instead of a stable version. On tagged releases this should always be the SemVer version no matter what is used.
…ase notes This allows an argument called 'create-pre-release' to be used when calling the cake build script for specifically setting the milestone to the generated SemVer version, instead of a stable version. On tagged releases this should always be the SemVer version no matter what is used.
(GH-597) Add ability to select pre-release or stable release notes
In the current stable release of cake.recipe release notes are always created using a MajorMinorPatch version, however, in the latest development version, it is created using a SemVer version instead.
Instead of having the ability to only use 1 or the other, I suggest adding support for a specific argument that can be passed when running the cake script to select whether semver or majorminorpatch version should be used for the milestone.
As an example:
Creating release notes without a specific argument, would use MajorMinorPatch as the default (to keep it backward compatible), but running the cake script with something along the lines of
--create-pre-release
would use a semantic version instead (ie1.0.0-beta.1
).The text was updated successfully, but these errors were encountered: