Skip to content

docs(changelog): Use ### format for Breaking Changes sections#1060

Merged
runningcode merged 2 commits intomainfrom
no/format-changelog-breaking-changes
Jan 23, 2026
Merged

docs(changelog): Use ### format for Breaking Changes sections#1060
runningcode merged 2 commits intomainfrom
no/format-changelog-breaking-changes

Conversation

@runningcode
Copy link
Contributor

@runningcode runningcode commented Jan 22, 2026

Summary

Improve the Unreleased section of CHANGELOG.md with the following changes:

  • Standardize Breaking Changes sections to use ### Breaking Changes heading format instead of **Breaking Changes**: for consistency with other section headings like Features, Fixes, Dependencies, and Internal
  • Link Size Analysis and Build Distribution features to their respective documentation pages
  • Simplify and consolidate feature descriptions to focus on user-facing functionality
  • Remove implementation details in favor of high-level feature descriptions

🤖 Generated with Claude Code

Standardize Breaking Changes sections to use ### heading format
instead of **Breaking Changes**: for consistency with other
section headings like Features, Fixes, and Dependencies.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Use ### format for Breaking Changes sections
- Link Size Analysis and Build Distribution to documentation
- Simplify and consolidate feature descriptions
- Remove implementation details in favor of user-facing features

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@runningcode runningcode requested a review from romtsn January 23, 2026 08:18
@runningcode runningcode merged commit 2e03d1c into main Jan 23, 2026
19 checks passed
@runningcode runningcode deleted the no/format-changelog-breaking-changes branch January 23, 2026 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants