The v1.0.0-gamma.6 release didn't mention #1398 as a BREAKING CHANGE

[trivikr]

Describe the bug
The v1.0.0-gamma.6 release didn't mention #1398 as a BREAKING CHANGE

• Refs: The v1.0.0-gamma.5 release didn't mention #1379 as a breaking change #1395 (comment)
• Release Changelog: https://github.com/aws/aws-sdk-js-v3/releases/tag/v1.0.0-gamma.6

SDK version number
v1.0.0-gamma.6

To Reproduce (observed behavior)

• The message with BREAKING CHANGE: was added in the footer of the commit message 9fedaa9
  • Conventional commits docs: https://www.conventionalcommits.org/en/v1.0.0/#summary
• In release notes https://github.com/aws/aws-sdk-js-v3/releases/tag/v1.0.0-gamma.6, the commit is mentioned under "New features" instead of breaking changes

Expected behavior

• The commits with BREAKING CHANGE in footer should be listed as a breaking change in a release
• Even better, the commits with ! in commit after type/scope should be listed as breaking change as documented in The v1.0.0-gamma.5 release didn't mention #1379 as a breaking change #1395

[github-actions]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.