Repository navigation
fix(deps): pin patched LiteLLM and repair integration CI - #460
Merged
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8502738. Configure here.
benjibc
approved these changes
Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

The existing LiteLLM pin blocks consumers that require the security fixes for GHSA-3cv6-jpf6-8222. Pin tested LiteLLM 1.105.0 and require tested MCP 1.30.0 on its supported v1 API; fresh installs otherwise select MCP v2, which removed
streamablehttp_client.Repair the integration failures exposed by the upgrade:
Sandbox.create()and publicfilesAPI so sandbox access tokens reach file/command requests. Preserve older code-interpreter SDK support and sandbox cleanup. Pin the tested dev SDK to 2.34.0; newer releases force OpenTelemetry changes incompatible with the currently locked optional adapters. Update HTTP/2 dependencies to patched releases.EP_KLAVIS_MODEL. Add always-running judging, authorization, dataset-adapter, and sandbox-compatibility tests. When live Klavis credentials are present, failed rollouts and service errors fail the test rather than returning a passing zero-score evaluation.Validation:
Klavis live tests require their existing environment variables when run manually. Core CI runs their offline checks and explicitly skips live Klavis evaluations without credentials. This PR adds no secret mappings or credential examples; the workflow and
.env.examplematch main. E2B and Fireworks tracing live tests remain enabled.Local validation of credential-wiring removal: 6 Klavis offline tests passed and 2 live tests explicitly skipped with both Klavis variables unset; Ruff and diff checks passed. Final CI: 17/17 checks passed on cleanup commit
4bc87f2ea2a1984d61a2b6ae7c053d27c2954ccd, including all 12 Python 3.10–3.12 core-test shards. Python CI and live Fireworks tracing both passed.