chore(release): 5.49.0 - #1045
Merged
Merged
Conversation
…ished one #990 branched from 2df53a2 on 2026-08-07, when the entries now dated 5.46.0 were still under [Unreleased]. It added its own entry to that block, and eight days later the squash merge applied the hunk by context — into a section that had since been released. So 5.46.0's published changelog claimed a feature it does not contain, and the BDC work would have shipped in the next release undocumented. Moved to [Unreleased] under a `### Changed` heading, with the two label-shape fixes and the ticker count added, since those are what a reader upgrading actually needs. 5.46.0 keeps its other 22 entries unchanged. Worth knowing for any long-lived branch: a CHANGELOG hunk written against [Unreleased] does not follow that heading when a release is cut underneath it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Seven entries, one Changed and six Fixed. The headline is section extraction: a 10-K written with colon-separated item headers went from one section to fifteen, and Item 1C (Cybersecurity, mandatory since December 2023) and Item 16 now resolve on filings whose table of contents omits them — which was most modern 10-Ks. Across the parity corpus the new parser moved from level with the deprecated one to ahead of it on 10-K, +0.1% to +3.4%. Also folds in the BDC changelog entry that #990 landed under the already published 5.46.0 section: its branch predated that release, so the squash merge placed the hunk by context into a section that had since been dated. Co-Authored-By: Claude Opus 5 (1M context) <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.
Seven entries — one Changed, six Fixed. Version
5.48.0→5.49.0(minor: user-visible behaviour changes).What users get
Section extraction is the headline, and the change is large. Across the parity corpus the new parser moved from level with the deprecated
ChunkedDocumentto ahead of it on 10-K:Item 1: Businessreturned one section where the legacy parser found fifteen — the vocabulary accepted a period or nothing, and a filer picks one separator for the whole document, so all 23 item patterns failed together.TenK.itemswas['Item 8']on real filings.TwentyF.items, and two deprecation-warning defects round out the Fixed section.Also folded in
#990's changelog entry had landed under
## [5.46.0] - 2026-08-07, a release published eight days before that PR merged: its branch predated the release, so the squash merge matched the hunk by context into a section that had since been dated. So 5.46.0 claimed a feature it does not contain, and this release would have shipped the BDC work undocumented. Moved to the 5.49.0 section here, which supersedes #1044.Fold checks (per the runbook)
🤖 Generated with Claude Code