Affected version
Reports that share this version, grouped in one feed.
Reading `AIMessage.content_blocks` for a message with a non-standard Anthropic content block containing an `index` key silently deletes that key from the original `message.content` because the fallback branch pops `index` from the same dict object stored in the message. This also affects `model_provider="bedrock"` via bedrock.py importing the same function.
ChatAnthropic in langchain-anthropic 1.6.1 sends top_k=10 to claude-opus-5, which Anthropic has deprecated for Opus 4.7 and later, resulting in a 400 BadRequestError. The client should validate locally and reject unsupported parameters before making a network request.
ChatAnthropic._assert_valid_model_configuration() only rejects manual thinking for models starting with claude-opus-5. Anthropic also rejects manual thinking for claude-opus-4-7, claude-opus-4-8, and claude-sonnet-5, so LangChain forwards invalid requests and the API returns HTTP 400.
`InMemoryVectorStore` does not override `_select_relevance_score_fn`, so `similarity_search_with_relevance_scores` and the `similarity_score_threshold` retriever raise `NotImplementedError` even though the store computes cosine similarity internally.
In langchain-core, `merge_configs` calls `ensure_config` on each input, which injects `DEFAULT_RECURSION_LIMIT = 25` when absent. This makes an explicitly provided `recursion_limit=25` indistinguishable from the injected default, causing it to be silently removed from the merged config.
The UsageMetadataCallbackHandler in langchain_core only records token usage when the response's response_metadata contains a 'model_name' key. If model_name is absent, usage_metadata is silently discarded, defeating the purpose of the callback and causing silent data loss in usage tracking for custom or third-party chat models.
XMLOutputParser.parse() raises OutputParserException for valid XML where a non-declaration element has an encoding attribute and the opening tag is followed by a newline. The regex used to remove the XML declaration is too broad and matches such element tags, causing the parser to remove the opening tag and produce malformed XML.