Skip to content

Add the 0.6.0 changelog - #59

Merged
emilk merged 2 commits into
release-0.6from
emilk/changelog-0.6
Aug 28, 2026
Merged

Add the 0.6.0 changelog#59
emilk merged 2 commits into
release-0.6from
emilk/changelog-0.6

Conversation

@emilk

@emilk emilk commented Aug 28, 2026

Copy link
Copy Markdown
Member

Related

What

The 0.6.0 changelog entry: generated with ./scripts/generate_changelog.py --version 0.6.0, then sorted into ⚠️ Breaking changes / New features / Performance / Other improvements, per the RELEASES.md step that asks for one line per feature and per break. 22 PRs from the generator, plus a summary paragraph and a two-sentence "breaking, in brief" for the migration.

Two hand edits the generator cannot make:

#37 and #31 appear twice each, in the same style as #19 in the 0.4.0 entry: #37 is a new feature and a break for hand-written LogicalType impls, #31 is a break and the reason Error went from 96 to 24 bytes.

Not included: the "Bump the version to 0.6.0" commit that opens the branch, and #58's own line is in place should it merge first — everything still open (#34, #47) will need a line if it lands before the release.

Testing

typos passes. No code changes.

Compatibility

Documentation only.

🤖 Generated with Claude Code

Generated with `./scripts/generate_changelog.py --version 0.6.0`, then
sorted into sections per `RELEASES.md`. Two hand edits the generator
cannot make:

* #24 is added by hand — it was merged into #23's branch before #23
  landed, so it never appears in this branch's history.
* #48 is listed under the name the release ships (`data_type()`), not the
  `datatype()` its PR title used before #50 renamed it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Comment thread CHANGELOG.md Outdated
@emilk
emilk marked this pull request as ready for review August 28, 2026 11:55
@emilk
emilk merged commit ac19155 into release-0.6 Aug 28, 2026
6 checks passed
@emilk emilk mentioned this pull request Aug 28, 2026
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