chore(deps): weekly dependency update

[github-actions]

Automated weekly dependency update via python scripts/update-matrix-latest.py && uv lock --upgrade.

⚠️ Provider SDK packages changed. A human needs to re-record cassettes locally before merging.

Summary by Sourcery

Update the Python dependency matrix and lockfile to current package versions, including major provider SDK upgrades.

Enhancements:

• Refresh the Python dependency matrix and lockfile to newer releases across provider SDKs, agent frameworks, evaluation tools, and supporting libraries.

Tests:

• Update dependency resolution metadata for the refreshed package set; provider integration cassettes require re-recording before merge.

[sourcery-ai]

Reviewer's Guide

Automates the weekly dependency refresh by upgrading the matrix’s latest provider/integration SDKs and regenerating the uv lockfile, while retaining historical test versions. Review should prioritize compatibility and lockfile resolution changes, and human cassette re-recording is required before merge.

Flow diagram for the weekly dependency refresh

flowchart LR
    A["Run update-matrix-latest.py"] --> B["Upgrade latest provider and integration SDKs"]
    B --> C["Run uv lock --upgrade"]
    C --> D["Regenerate uv.lock"]
    D --> E["Re-record provider cassettes"]
    E --> F["Review compatibility and merge"]

Loading

File-Level Changes

Change	Details	Files
Advances the matrix’s latest provider and integration package versions while preserving pinned historical compatibility entries.	Updates latest versions across OpenAI, Anthropic, Cohere, agent frameworks, model providers, orchestration libraries, and related integrations. Keeps existing version-specific matrix entries unchanged for regression coverage. Requires local cassette re-recording because provider SDK behavior and outputs may have changed.	py/pyproject.toml
Regenerates the uv dependency lockfile to resolve the upgraded dependency graph.	Refreshes direct and transitive package versions and metadata based on the updated matrix. Includes a large lockfile diff that warrants focused inspection for unexpected dependency, platform, or constraint changes.	py/uv.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Fixed security issues:

• cryptography (link)
• gitpython (link)
• mcp (link)
• pyjwt (link)
• python-multipart (link)
• starlette (link)
• urllib3 (link)

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="py/pyproject.toml" line_range="287" />
<code_context>

 [tool.braintrust.matrix.openai]
-latest = "openai==2.33.0"
+latest = "openai==3.6.0"
 "1.92.0" = "openai==1.92.0"
 "1.77.0" = "openai==1.77.0"
</code_context>
<issue_to_address>
**issue (testing):** The matrix now installs each upgraded SDK under the existing `latest` cassette directory, but this diff does not update those recordings. Integration tests therefore replay cassettes produced by the previous SDK versions and fail on changed request/response formats, or silently fail to validate the upgraded SDK behavior.

**Triggers:** When the integration test sessions for any upgraded provider run before the cassettes are re-recorded.

**Suggested fix:** Re-record and commit the `cassettes/latest` fixtures for every upgraded provider, or defer each `latest` pin until its corresponding cassette is updated.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (testing): The matrix now installs each upgraded SDK under the existing latest cassette directory, but this diff does not update those recordings. Integration tests therefore replay cassettes produced by the previous SDK versions and fail on changed request/response formats, or silently fail to validate the upgraded SDK behavior.

Triggers: When the integration test sessions for any upgraded provider run before the cassettes are re-recorded.

Suggested fix: Re-record and commit the cassettes/latest fixtures for every upgraded provider, or defer each latest pin until its corresponding cassette is updated.

[github-actions]

Superseded by a newer automated dependency update.