LangChain Core 1.6.12 Fixes Streaming Block Extras
One bug fix, one version bump: extras now ride along on content-block-start events again, so streaming metadata stops vanishing mid-chunk.
In short
langchain-core 1.6.12 is a single-fix patch: extras are propagated on content-block-start events again, and nothing else is listed as changed since 1.6.11.
At a glance
- The release page lists exactly two entries for langchain-core 1.6.12: the version bump and one bug fix.
- The fix is titled 'propagate extras on content-block-start events' and lands as PR #41272.
- The bump itself is PR #41277; the comparison baseline is the previous release, 1.6.11.
- The page dates the release to October 16 and points at commit bd5b134.
langchain-core 1.6.12 ships one substantive change: extras are propagated on content-block-start events again. Beyond the version bump itself, the release page lists nothing else.
The whole changelog, in two lines
Measured against 1.6.11, the change list has two entries. PR #41277 is the release commit that moves the version number. PR #41272 carries the actual fix, titled 'propagate extras on content-block-start events'.
The page dates the release to October 16 and points at commit bd5b134. It names no affected providers and says nothing about how long the behavior had been wrong.
What extras do inside a stream
A streamed model response arrives as a sequence of blocks, and a content-block-start event announces where one begins. Extras are the side fields attached to that block. Drop them at the start event and the text still arrives while the information about it does not.
A plain chat surface barely notices. Code that routes blocks by kind — prose, tool call, reasoning step — leans on exactly those fields, which is how a one-line changelog ends up mattering in production.
What the note does not establish
The fix title names neither the specific fields involved nor the integrations affected. Our reading of which metadata is at stake follows from what those event names mean inside langchain-core, not from any statement on the release page. The authoritative answer is the diff in PR #41272.
Whether 1.6.12 repairs a regression introduced in a recent earlier patch is also not stated there, and we did not verify it.
Whether to upgrade
For anything pinned to 1.6.x this is a low-risk bump: one bug fix, no announced breakage. Teams that consume streaming events directly and have recently lost block metadata have an obvious first thing to try. Everyone else can take it on a normal upgrade cadence.
The full notes sit on GitHub.
FAQ
What changed in langchain-core 1.6.12?
One fix: extras are propagated on content-block-start events again (PR #41272), plus the release commit for the version bump (PR #41277).
Is langchain-core 1.6.12 a breaking release?
The release page lists no breaking changes between 1.6.11 and 1.6.12 — only the single fix and the version bump.
Where can I see exactly what the fix touched?
In the diff for PR #41272; the release note gives the title only and does not enumerate the fields or integrations involved.
