chore(deps): weekly dependency update - #18
Conversation
Reviewer's GuideAutomates 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 refreshflowchart 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"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
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
<locationpath="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>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| [tool.braintrust.matrix.openai] | ||
| latest = "openai==2.33.0" | ||
| latest = "openai==3.6.0" |
There was a problem hiding this comment.
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.
Automated weekly dependency update via
python scripts/update-matrix-latest.py && uv lock --upgrade.Summary by Sourcery
Update the Python dependency matrix and lockfile to current package versions, including major provider SDK upgrades.
Enhancements:
Tests: