Add all code changes (features, deprecations, and enhancements) under the Unreleased topic to track changes for
the next release. Once the changes are released,
rename Unreleased topic with the new version tag. Finally, create a new Unreleased topic for future changes.
Wait!, you don't need to do this manually - use ReleaseZri
- Add the
--no-changesflag to thecreatecommand to continue the release note generation without change logs in the unreleased section.
- Add
RZ_TOPtemplate variable and set it via--top=<content_mardown>. This feature is helpful for adding important messages about releases. i.e, Nightly build warning.
- Remove
vfromRZ_VERSIONtemplate variable. - Add new template variables
RZ_RZVERSION,RZ_DATE, andRZ_TIME.
- Add
Unreleasedwhile updating the changelog with the latest version
- Updated local sample template
- Initial version
- Initial version
- Initial version