Backfill changelog entries for 2026.4.0–2026.6.0 - #75
Merged
Conversation
These releases shipped without changelog entries (the towncrier fragments dir is empty and the changelog is hand-maintained, so it had lagged at 2026.3.0). Reconstruct the entries from the git history of each tag. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The changelog had lagged at
2026.3.0even though2026.4.0,2026.5.0, and2026.6.0were all released. The towncrier fragments dir is empty (.gitkeeponly) anddocs/changelog.rstis hand-maintained, so those releases never got entries. This reconstructs them from each tag's git history.Entries added (descending, above 2026.3.0)
tickers_as_of(retain historically exported symbols; no new changes syms #69)Docs-only;
just check-allpasses.🤖 Generated with Claude Code