Repository navigation
chore(deps): weekly dependency update - #849
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 93a3ba26b1
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
|
|
||
| [tool.braintrust.matrix.mistralai] | ||
| latest = "mistralai==2.10.1" | ||
| latest = "mistralai==3.0.0" |
There was a problem hiding this comment.
Updating this integration across a major SDK release without refreshing its latest cassettes leaves test_mistral(latest) replaying Mistral 2.9/2.10 exchanges (for example, the request fixtures under integrations/mistral/cassettes/latest/ still identify those clients). That session selects the latest cassette directory while CI runs VCR in replay-only mode, so this change cannot validate the request/response behavior of the newly shipped v3 client. Re-record the Mistral latest fixtures and make any compatibility adjustments the v3 playback exposes.
AGENTS.md reference: AGENTS.md:L194-L205
Useful? React with 👍 / 👎.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 15ebf33f13
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
|
|
||
| [tool.braintrust.matrix.anthropic] | ||
| latest = "anthropic==1.8.0" | ||
| latest = "anthropic==1.11.0" |
There was a problem hiding this comment.
The 1.11.0 bump is only partially re-recorded: for example, test_anthropic_beta_messages_create_captures_compaction_metadata.yaml still identifies Anthropic/Python 1.8.0, even though that test explicitly runs only for the latest matrix entry; the sessions-events cassette is likewise unchanged. Because test_anthropic(latest) selects this directory and CI is replay-only, these paths continue replaying 1.8-era traffic rather than validating the newly pinned client. Re-record the remaining latest-only tests with 1.11.0.
AGENTS.md reference: AGENTS.md:L194-L204
Useful? React with 👍 / 👎.
|
|
||
| [tool.braintrust.matrix.mistralai] | ||
| latest = "mistralai==2.10.1" | ||
| latest = "mistralai==3.0.0" |
There was a problem hiding this comment.
Fresh evidence after the earlier review comment is that the refresh remains incomplete: 14 files in mistral/cassettes/latest, covering chat, agents, OCR, and auto-instrumentation, are unchanged and still record mistral-client-python/2.9.0 or 2.10.0. Thus test_mistral(latest) installs v3 but replays pre-v3 exchanges for those endpoint families in replay-only CI, leaving much of the major-version upgrade unvalidated. Re-record the complete latest session rather than only the conversations/audio/FIM subset.
AGENTS.md reference: AGENTS.md:L194-L204
Useful? React with 👍 / 👎.
1 participant
Automated weekly dependency update via
python scripts/update-matrix-latest.py && uv lock --upgrade.