You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Automating releases, using pre-releases (RCs) like -alpha.1 doesn't allow to properly generate change logs that make sense to the user.
Assuming you have: 1.0.0-rc.1, 1.0.0-rc.2, 1.0.0
Then for the rc versions, I want to see the changes up to he previous version, including rcs.
When releasing the proper 1.0.0, I want all changes up to the previous proper release.
Describe the solution you'd like
I guess what I want is --ignore-pre-releases. By default (=false) a patch release (using --max-patch-releases) includes pre-releases. And so it would stop after x patch releases.
Enabling the switch (--ignore-pre-releases) would ignore the tag information, and continue to scoop up log entries until the next (non-pre-release) version is found.
Is your feature request related to a problem? Please describe.
Automating releases, using pre-releases (RCs) like
-alpha.1
doesn't allow to properly generate change logs that make sense to the user.Assuming you have: 1.0.0-rc.1, 1.0.0-rc.2, 1.0.0
Then for the
rc
versions, I want to see the changes up to he previous version, includingrc
s.When releasing the proper
1.0.0
, I want all changes up to the previous proper release.Describe the solution you'd like
I guess what I want is
--ignore-pre-releases
. By default (=false) a patch release (using--max-patch-releases
) includes pre-releases. And so it would stop afterx
patch releases.Enabling the switch (
--ignore-pre-releases
) would ignore the tag information, and continue to scoop up log entries until the next (non-pre-release) version is found.Describe alternatives you've considered
…
Additional context
Follow up from: #59
The text was updated successfully, but these errors were encountered: