-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(release): changelog renderer should prefer breaking change explanation text #20798
fix(release): changelog renderer should prefer breaking change explanation text #20798
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 001c532. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
(commit.isBreaking ? '⚠️ ' : '') + | ||
(commit.scope ? `**${commit.scope.trim()}:** ` : '') + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
We always repeat the breaking change commit message and do not recognize breaking changes without the
!
being present.Expected Behavior
We recognize breaking changes with only
BREAKING CHANGE:
present (in accordance with the spec https://www.conventionalcommits.org/en/v1.0.0/), and we preferentially render the explanation text afterBREAKING CHANGE:
in the relevant section of the changelog.Related Issue(s)
Fixes #