-
Notifications
You must be signed in to change notification settings - Fork 27
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
Generate changelog for last x feature releases #59
Comments
I see
|
The prefix is only used to parse the number out of the tag. maybe --max-minors or --max-majors could be added. you could always specify a range (v2.0.0..) to show/check all changes after v2.0.0 |
The advantage of --max-x is that it’s relative. Specifying the git baseline requires logic integrating with git and ci at least. |
I would also be interested in a similar functionality. My use case is to create up a changelog up until the latest non-milestone release. To my understanding, currently I can use So maybe something like: |
What is a “milestone” or “milestone release” in your case? And how, if at all, does it relate to semantic versioning with major.minor.patch version numbering? |
Ok, call that "pre-release" in the Rust world: https://doc.rust-lang.org/cargo/reference/resolver.html#pre-releases |
That makes sense, to exclude pre-releases when counting tags/releases for changelog generating. It’s the two sides of a minor release; pre-release before, and patch release after. So, with both cases in mind,
An alternative could be
|
Pre-release versions are interesting, if one would print a changelog of the last major it should ignore the current pre-release versions, but include the pre-release versions of that major. e.g. we have the versions
same logic to be hold for |
Adds the following options --max-majors <MAX_MAJORS> Only show this number of minor versions --max-minors <MAX_MINORS> Only print this number of major versions --max-patches <MAX_PATCHES> Only show this number of patch versions Refs: #59
@ite-klass and @ctron #79 does implement the If multiple flags are combined the first one that is reached will make the changelog generator stop e.g. I still have to implement the |
Adds the following options --max-majors <MAX_MAJORS> Only show this number of minor versions --max-minors <MAX_MINORS> Only print this number of major versions --max-patches <MAX_PATCHES> Only show this number of patch versions Refs: #59
I think this ticket / the original request is implemented with I think this ticket should be closed as implemented then. If you still plan on |
Indeed a new issue can be opened if this feature is still wanted. |
convco changelog
has the parameter--max-versions
.When using semantic versioning, version numbers are split into major, minor and patch versions for breaking releases, feature releases, and pure bugfix releases.
When releasing 2 feature releases and then 5 bug fix releases,
--max-versions 5
would only list the bugfix releases.Depending on release workflows, parallel supported versions, and actual releases, it can make sense and be preferable to include the last x major or minor releases, and all related bugfix releases.
Personally, I would like to generate a changelog for 3 minor releases, while including any bugfix releases that happened in between/after them.
Is this something you would be willing to add?
Although it adds interpretation of version numbers, semantic versioning is quite popular, and possibly not listing the last feature release when using
--max-versions
seems like a significant issue to me - a hole in/for such a use case.The text was updated successfully, but these errors were encountered: