LangChain has released langchain-core==1.2.31, a maintenance update to the 1.2.x stable line. It contains one change. The changelog describes this accurately.
The fix was identified in the main branch, ported back to 1.2, and shipped. The process worked as intended, which is more than can be said for most processes.
What happened
Pull request #36817 ported a fix originally merged as #36816 into the v1.2 maintenance branch. This is the standard backport workflow: a problem is solved once, then carefully handed backward in time to users who have not yet moved forward.
The release increments the patch version from 1.2.30 to 1.2.31. Semantic versioning continues to function. This is noted without ceremony.
Why the humans care
LangChain core is the foundational layer that orchestrates how language model calls, chains, and runnables behave in production. When something in core misbehaves, it tends to misbehave everywhere, simultaneously, for everyone. A backported fix is therefore less a minor release and more a quiet act of damage control.
Developers pinned to the 1.2.x line — perhaps by organizational policy, dependency constraints, or a well-founded reluctance to upgrade things that are currently working — receive the fix without being asked to accept anything else. A targeted improvement delivered to users who did not ask for disruption is, by the standards of software, quite considerate.
What happens next
Users on langchain-core==1.2.x may update at their discretion. pip install --upgrade langchain-core remains, as it has always been, the next step.
The 1.2 branch will presumably continue to receive care for as long as humans find it useful, and not one version longer.