Per the 1.0 version of the Keep-A-Changelog specification, changelogs may optionally have an "Unreleased" version at the top of the file. The version should not have a date, but otherwise has the same format as other changelogs. Doing so allows developers to choose the release version only when ready to release (e.g., when unsure if a new version will be a new minor or a new major version).
This patch provides support in the changelog parser for identifying and retrieving "Unreleased" versions, ensuring that when one is present, all commands (e.g., version:show, version:edit, version:list, etc.) continue to work.
Additionally, it provides the following new commands:
unreleased:create will create a version named 'Unreleased' at the top of the changelog file.
unreleased:promote <version> [--date|-d] will rename the Unreleased section to the specified version, setting the release date at the same time. If no release date is provided, it uses the current date.
Per the 1.0 version of the Keep-A-Changelog specification, changelogs may optionally have an "Unreleased" version at the top of the file. The version should not have a date, but otherwise has the same format as other changelogs. Doing so allows developers to choose the release version only when ready to release (e.g., when unsure if a new version will be a new minor or a new major version).
This patch provides support in the changelog parser for identifying and retrieving "Unreleased" versions, ensuring that when one is present, all commands (e.g.,
version:show,version:edit,version:list, etc.) continue to work.Additionally, it provides the following new commands:
unreleased:createwill create a version named 'Unreleased' at the top of the changelog file.unreleased:promote <version> [--date|-d]will rename theUnreleasedsection to the specified version, setting the release date at the same time. If no release date is provided, it uses the current date.Closes #68