Repository navigation
test(langchain): record langsmith and bedrock mantle partner chat providers in drift snapshot - #2589
Conversation
…viders in drift snapshot The scheduled latest-deps job has failed on test_langchain_provider_drift since langchain added the langsmith, bedrock_mantle_anthropic and bedrock_mantle_openai partner chat providers. These are upstream additions with nothing removed, so regenerate the langchain-community 0.4 snapshot entry with update_provider_snapshot.py at langchain 1.4.8. Signed-off-by: Pouyanpi <13303554+Pouyanpi@users.noreply.github.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
@greptile review this PR |
[Low impact] This snapshot update appears safe to merge. SummaryUpdates the test snapshot for the
Reviews (2) · Last reviewed commit: "test(langchain): record langsmith and be..." · Reviewed by Greptile |
Description
The scheduled "Test with Latest Dependencies" job has failed since 2026-08-18 on the
test_langchain_provider_driftcanary. Newer langchain releases added three partner chat providers to_BUILTIN_PROVIDERS, so the discovered set drifted from the snapshot recorded at langchain 1.3.13 (added=['bedrock_mantle_anthropic', 'bedrock_mantle_openai', 'langsmith'], removed=[]).These are upstream additions with nothing removed, so this regenerates the langchain-community 0.4 snapshot entry via
update_provider_snapshot.pywith langchain 1.4.8 installed:langchain_version: 1.3.13 -> 1.4.8partner_chat_providers: addbedrock_mantle_anthropic,bedrock_mantle_openai,langsmithThe 0.3 series entry and
uv.lockare unchanged.Related Issue(s)
Failing run: https://github.com/NVIDIA-NeMo/Guardrails/actions/runs/42707955810
Verification
LANGCHAIN_PROVIDER_DRIFT_CHECK=1with langchain 1.4.8:tests/integrations/langchain/llm/test_version_compatibility.py14 passed.make test TEST=tests/integrations/langchain/llm/test_version_compatibility.py13 passed, 1 skipped (canary is skipped outside the latest-deps job).Not covered: the Windows / Python 3.12 job in the failing run also hit a
TimeoutErrorintests/server/experimental/test_guardrails_startup_cleanup.py::test_application_retains_failed_startup_until_cleanup_finishes[timeout-raise]. It passed on the other Windows jobs and is not addressed here.Summary by CodeRabbit