Repository navigation
framework-release: langchain-openai 1.6.7 → 1.7.1 #1129
Description
langchain-openai 1.7.1 is out; the PR lock pins 1.6.7.
| Framework | langgraph (extra langgraph) |
| Locked | 1.6.7 in python/constraints/adapter-contract-langgraph-py3.12.txt |
| Latest | 1.7.1 (minor bump), released 2026-10-12 |
| Release notes | https://github.com/langchain-ai/langchain/releases?q=%22langchain-openai%22 |
Results against the PR lock
langchain-openai==1.7.1 does not resolve against the PR lock, so it was installed unconstrained (needs co-bump).
Other locked packages that moved: ast-serialize 0.12.1 → 0.13.0, iniconfig 2.3.0 → 2.3.1, jsonpatch 1.33 → 1.35, jsonpointer 3.1.1 → 3.2.1, langchain-core 1.6.7 → 1.6.10, langgraph 1.2.14 → 1.2.15, langgraph-checkpoint 4.2.0 → 4.3.0, langgraph-sdk 0.4.6 → 0.4.7, langsmith 0.14.4 → 0.14.8, openai 3.24.0 → 3.31.0, orjson 3.12.0 → 3.13.0, pydantic 2.13.5 → 2.14.1, pydantic-core 2.46.5 → 2.50.1, ruff 0.16.10 → 0.17.0, starlette 1.7.0 → 1.8.0, tenacity 9.1.4 → 9.2.1, truststore 0.10.4 → 0.10.5.
| Check | Result |
|---|---|
| install | ✅ pass |
verify_frameworks.py --require-installed |
✅ pass |
pytest -q (skip guard armed) |
✅ pass |
smoke_example.py |
✅ pass |
Impact review (AI, advisory)
Risk: low. Recommended action: bump. Confidence: medium.
The range after 1.6.7 is 1.7.0 (adds a beta Decisions API wrapper and dependency bumps) and 1.7.1 (adds mid-conversation capability flags to model profiles). Neither touches the ChatOpenAI constructor kwargs, the http clients, max_retries, use_responses_api or the callback API the adapter uses. The only adjacent change is profile metadata, which is low risk. The compare diff would not render, so I read the release notes and two PR descriptions instead of the full diff.
| Symbol | Change | Where the adapter uses it | Upstream |
|---|---|---|---|
ChatOpenAI model profile resolution (_resolve_model_profile; new mid_conversation_system_messages / mid_conversation_to… |
behaviour | chat_model() / connection_kwargs() in langgraph.py: sets use_responses_api=False by default (§8 LangGraph row); only the profile metadata read by callers diffe… | source |
Reviewed by claude-sonnet-5-5 in https://github.com/Donkey-Development-Kit/donkey-development-kit/actions/runs/38400097553. Advisory only: this is not verification (§0.3), it never changes a docs/verified-apis.md §8 row, and a maintainer confirms any finding before acting on it.
Next action
Safe to bump. It needs the co-bumps listed above, which the recompile picks up. The nightly lock-refresh PR (lock-refresh.yml) may already carry it. Otherwise, from python/:
python scripts/compile_constraints.pypython scripts/generate_docs.pypython scripts/verify_frameworks.py --only langgraph --emit-verified, and record the rows indocs/verified-apis.md§8- the pre-PR gate (CONTRIBUTING.md §1)
Opened and kept current by framework-release-watch.yml (docs/ci.md). It closes this issue once the lock reaches this version.
Activity
github-actions commentedon Oct 14, 2026
The results changed.
langchain-openai==1.7.1does not resolve against the PR lock, so it was installed unconstrained (needs co-bump).Other locked packages that moved:
ast-serialize0.12.1 → 0.13.0,iniconfig2.3.0 → 2.3.1,jsonpatch1.33 → 1.35,jsonpointer3.1.1 → 3.2.1,langchain-core1.6.7 → 1.6.10,langgraph1.2.14 → 1.2.15,langgraph-checkpoint4.2.0 → 4.3.0,langgraph-sdk0.4.6 → 0.4.7,langsmith0.14.4 → 0.14.8,openai3.24.0 → 3.31.0,orjson3.12.0 → 3.13.0,pydantic2.13.5 → 2.14.1,pydantic-core2.46.5 → 2.50.1,ruff0.16.10 → 0.17.0,starlette1.7.0 → 1.8.0,tenacity9.1.4 → 9.2.1,truststore0.10.4 → 0.10.5.verify_frameworks.py --require-installedpytest -q(skip guard armed)smoke_example.pyRun: https://github.com/Donkey-Development-Kit/donkey-development-kit/actions/runs/38549203785
chore(deps): ship the framework releases in the nightly lock refresh (#…