LangChain Core 1.6.3 lets gateways name the model
The patch release overrides model name and provider in tracing metadata using the gateway response; three more entries cover tests and docs.
In short
LangChain published langchain-core 1.6.3 on September 11, and its only functional change lets the model name and provider in tracing metadata be overridden by what the gateway reports back.
At a glance
- langchain-core 1.6.3 shipped on September 11; the previous version was 1.6.2.
- The release page lists four entries: #40407, #40406, #40243, #40211.
- Only functional change: #40406 overrides model name and provider in tracing based on the gateway response.
- #40243 adds a test for the deprecated .text() access path; #40211 drops stale documentation sections.
- Absent from the notes: which gateways apply, which fields are read, whether the override can be disabled.
langchain-core 1.6.3 landed on September 11. Measured against 1.6.2, the release page carries four entries, and exactly one of them changes runtime behavior: pull request #40406 allows the model name and provider recorded in tracing metadata to be overridden by the gateway response. The release points at a commit starting 348c9dc.
The observability gap this closes
Route a call through a gateway or a router instead of straight to a provider, and your trace records the label your application configured — not necessarily the model that served the request. That gap turns per-model cost attribution into guesswork and makes a regression hard to pin on anything specific. #40406 reverses the priority: when the gateway answer carries a model and a provider, those values may replace the configured ones.
The notes stop short of the mechanics. They do not say which response fields are inspected, which gateway implementations were validated, or whether the override can be turned off. Anyone depending on the behavior should read the pull request rather than infer it from the changelog line.
The other three entries
- #40407 — the version bump to 1.6.3 itself.
- #40243 — test coverage for the deprecated .text() access path, so a future removal does not break callers quietly.
- #40211 — documentation cleanup, removing stale Args and Raises sections on FileCallbackHandler._write and ChatGeneration.set_text.
Who should care
This is a patch release, not a milestone. Teams calling providers directly mostly get tidier docstrings and one more test. Teams with a gateway in front get the groundwork for traces that name the model that answered instead of the one that was requested.
Whether the build is already installable from PyPI as of this report, and whether sibling packages follow, is not stated on the release page. The only thing we verified is that GitHub release entry.
FAQ
What changed in langchain-core 1.6.3?
Four entries since 1.6.2: the version bump (#40407), the tracing override for model name and provider based on the gateway response (#40406), a test for the deprecated .text() access path (#40243), and a documentation cleanup (#40211).
Why does overriding the model name and provider in tracing matter?
When a request passes through a gateway, the model that answers can differ from the one configured. If tracing adopts the values returned by the gateway, cost attribution and debugging refer to the model actually used.
Should I upgrade from 1.6.2 to 1.6.3?
The release page lists no breaking changes and no migration steps. The upgrade matters most for gateway-fronted deployments; without a gateway it mainly brings test and documentation changes.
