v1.8.0

• ignore-authors flag was added so that any prs submitted by this author will not be included in the generated release note. This feature is useful for prs created by bots (ex. dependabot).

v1.7.1

• Fixes the precedence of labels so that the misc label takes higher precedence than bug or enhancement labels. This makes more sense with common cases such as a PR that is a bug fix for an unreleased feature. We would expect that PR to be placed in the misc section rather than the bug section.

v1.7.0

• Added a flag ignore-release-regex that will ignore any releases that match that regex when generating a release note

v1.6.0

• Added new release-version required flag for the generate command. It is used to figure out where to start fetching pull requests for the generated release note. If the version passed into the release-version flag is a major/minor version, it will fetch starting from the last released major/minor version. If the version passed is a patch version, it will fetch starting from the last release regardless of if it was a major/minor/patch. As a result, this means that the release note generated for any major/minor versions will include the pull requests that were released as a part of previous patch versions.

v1.5.0

• Revert sub section changes, refer to this comment to know why.
• Renamed No Impact section to Miscellaneous, meaning it no longer accepts the label release/no-impact and is now replaced with misc

v1.4.0

• Added sub sections to the No Impact section within the release note generation
  • These sub sections include refactor, testing, dependencies and internal. A pr is put into that subsection through the corresponding label. PRs can still be put into the general No Impact section with the release/no-impact label.

v1.3.0

• The generate command accepts a last-commit-SHA which will generate a release note with all prs merged before this commit SHA (and after the latest release)

v1.2.0

• Fixes the generate command to be able to be used for branches other than master
• Changes some templating of the generated release note

v1.1.0

Reformat the release note template

• Spacing between sections will be smaller
• Section header text will be smaller

v1.0.0

• Added generate command that will construct a release note using all the pull requests merged after the latest release of your repository
• Added validate command that will check to see if the pull request has the appropriate labels for creating a release note