Skip to content

chore(deps): weekly dependency update - #21

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
deps/weekly-update-2026-09-21
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
deps/weekly-update-2026-09-21

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 21, 2026 •

Copy link
Copy Markdown

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

Refresh the Python dependency matrix and lockfile to the latest supported package versions.

Enhancements:

  • Update the dependency matrix to newer releases across provider SDKs, agent frameworks, evaluation tools, and supporting packages.

Build:

  • Regenerate the Python lockfile with upgraded dependency resolutions.

Tests:

  • Re-record provider integration cassettes locally to reflect the updated SDK behavior before merging.

@sourcery-ai

sourcery-ai Bot commented Sep 21, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Automated weekly dependency refresh updates the matrix’s latest pins across provider SDKs, agent integrations, and test tooling, then regenerates the lockfile; reviewers should verify lockfile resolution and require cassette re-recording before merge.

File-Level Changes

Change Details Files
Advance the dependency matrix’s latest provider and tooling versions while preserving older compatibility entries.
  • Update latest pins for multiple provider SDKs and integrations, including OpenAI, Anthropic, Cohere, LiteLLM, Google, Pydantic AI, and agent frameworks.
  • Keep historical version entries unchanged for matrix coverage.
  • Regenerate the uv lockfile with the dependency upgrade command, producing a large transitive dependency diff.
  • Require local cassette re-recording because provider SDK behavior and/or serialization may have changed.
py/pyproject.toml
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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue

Fixed security issues:

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.16.2"
 "1.92.0" = "openai==1.92.0"
 "1.77.0" = "openai==1.77.0"
</code_context>
<issue_to_address>
**issue (broader_impact):** The provider matrix now installs new SDK versions for the `latest` nox sessions, but this PR does not update the corresponding cassette recordings. CI configures VCR with `record_mode = "none"` under CI/GitHub Actions, so the latest-version integration tests fail when the new SDK requests do not match the existing recordings.

**Triggers:** When CI runs any provider integration session against the updated `latest` pin.

**Suggested fix:** Re-record and commit the `cassettes/latest` fixtures for each changed provider, or keep the old pins until the recordings are updated.
</issue_to_address>

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

Comment thread py/pyproject.toml

[tool.braintrust.matrix.openai]
latest = "openai==2.33.0"
latest = "openai==3.16.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (broader_impact): The provider matrix now installs new SDK versions for the latest nox sessions, but this PR does not update the corresponding cassette recordings. CI configures VCR with record_mode = "none" under CI/GitHub Actions, so the latest-version integration tests fail when the new SDK requests do not match the existing recordings.

Triggers: When CI runs any provider integration session against the updated latest pin.

Suggested fix: Re-record and commit the cassettes/latest fixtures for each changed provider, or keep the old pins until the recordings are updated.

@github-actions

Copy link
Copy Markdown
Author

Superseded by a newer automated dependency update.

@github-actions github-actions Bot closed this Sep 28, 2026
@github-actions
github-actions Bot deleted the deps/weekly-update-2026-09-21 branch September 28, 2026 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant