Repository navigation
feat(server-utils): Support @mistralai/mistralai v3 - #25827
Merged
Merged
Conversation
Widen the orchestrion range to <4. The files, classes and methods we hook and the response and stream fields we read are unchanged in v3. Run the node integration suite on 3.3.0 and keep v2 covered with a small mistral-v2 suite. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
bugbot run |
Contributor
size-limit report 📦Compared: 9bc8be2 (PR test merge using develop at c6ac34c) Against: c6ac34c (develop) · base run #63981 ✅ Baseline matches: this diff contains only this PR's changes.
|
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 16fa6c3. Configure here.
Contributor
Optional E2E testsSome optional checks were not successful. They do not block the merge. 5 not successful, 62 successful. See the run.
Successful checks
|
Bun's runtime cannot inject the diagnostics channels and the mistral suite is untriaged on Deno, so the v2 suite fails there for the same reasons. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mistralai/mistralai v3 statically imports its optional peer @livekit/rtc-node, so Bun cannot bundle the scenarios. The mistral-v2 suite still covers Mistral in the bundled build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chargome
marked this pull request as ready for review
October 29, 2026 09:37
chargome
requested review from
andreiborza,
msonnb,
mydea and
nicohrubec
and removed request for
a team,
msonnb and
mydea
October 29, 2026 09:37
nicohrubec
approved these changes
Oct 29, 2026
andreiborza
approved these changes
Oct 29, 2026
mydea
added a commit
that referenced
this pull request
Oct 30, 2026
Mistral 3.x is instrumented since #25827. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
@mistralai/mistralai3.x is out (latest 3.3.0), but our orchestrion range stopped at<3, so Mistral spans silently disappear on v3. Everything we hook is unchanged in v3: same files, classes and methods, and the response and stream fields we read are still there. The 3.0.0 breaking changes don't touch anything we use, so widening the range to<4is enough.