Skip to content

docs: migrate changelog history to the changesets format - #346

Merged
QuentinRoy merged 1 commit into
mainfrom
claude/changelog-format-migration-308a58
Sep 14, 2026
Merged

QuentinRoy merged 1 commit into
mainfrom
claude/changelog-format-migration-308a58

Conversation

@QuentinRoy

Copy link
Copy Markdown
Owner

Pull request #132 is the Changesets release action's "Version Packages" pull request. It inserts new release notes as a ## <version> heading followed by Major Changes, Minor Changes, and Patch Changes sections, right after the changelog's introductory paragraph.

The existing history predates Changesets and used a different convention: the heading level varied with release type (# for a major release, ## for minor, ### for patch), and each release grouped its entries under Features, Bug Fixes, and BREAKING CHANGES. Once pull request #132 lands, its ## <version> heading would sit at the same level as the old releases' ### section headings, so the file's structure would no longer nest correctly.

This rewrites every past release to use the same heading level and section names Changesets produces: BREAKING CHANGES notes become Major Changes, Features become Minor Changes, and Bug Fixes become Patch Changes. A few older releases had a breaking-change note that just restated a feature's description; those are now a single Major Changes entry instead of two.

No content was removed, only reorganized and relabeled; compare links, dates, commit hashes, and issue references are all preserved.

Pull request #132 (the Changesets release action) inserts new
entries as a `## <version>` heading with `Major Changes`,
`Minor Changes`, and `Patch Changes` sections. The existing history
used a different heading level per release type (`#` for major,
`##` for minor, `###` for patch) and labeled its sections `Features`,
`Bug Fixes`, and `BREAKING CHANGES`, so once that pull request lands
its heading would sit at the same level as the old sections'
subheadings instead of above them.

Rewrite every past release to use the same `##` heading and the same
three section names, mapping `BREAKING CHANGES` notes to
`Major Changes`, `Features` to `Minor Changes`, and `Bug Fixes` to
`Patch Changes`. Where a breaking-change note duplicated a feature's
description, keep a single entry under `Major Changes` instead of
listing it twice.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Sep 14, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: d3139cd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@QuentinRoy
QuentinRoy merged commit fce3493 into main Sep 14, 2026
5 checks passed
@QuentinRoy
QuentinRoy deleted the claude/changelog-format-migration-308a58 branch September 14, 2026 12:48
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.

1 participant