This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and publish to npm
yourself or [setup this action to publish
automatically](https://github.com/changesets/action#with-publishing). If
you're not ready to do a release yet, that's fine, whenever you add more
changesets to main, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
`main` is currently in **pre mode** so this branch has prereleases
rather than normal releases. If you want to exit prereleases, run
`changeset pre exit` on `main`.
⚠️⚠️⚠️⚠️⚠️⚠️
# Releases
## @mastra/client-js@1.60.0-alpha.12
### Minor Changes
- Allow `querySpans()` to sort by `model` or `provider`.
([#30096](https://github.com/mastra-ai/mastra/pull/30096))
```ts
orderBy: [{ field: 'model', direction: 'asc' }];
```
### Patch Changes
- The generated route types for scores now include the `SCORER` and
`PROCESSOR` entity types, matching the entity types experiments can
emit. ([#30145](https://github.com/mastra-ai/mastra/pull/30145))
- Add span-local error counts.
([#30088](https://github.com/mastra-ai/mastra/pull/30088))
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/factory@0.28.0-alpha.14
### Minor Changes
- A card's sandbox now stops as soon as the card is done with that
context, instead of idling until the provider times it out.
([#29981](https://github.com/mastra-ai/mastra/pull/29981))
- When a card moves out of the last phase of a context into a phase that
runs in another one, Factory stops that context's sandbox. Triage →
Planning stops the triage sandbox; Planning → Building keeps the shared
`work` sandbox running. A run still in flight on the session keeps its
sandbox until it ends.
- When a card finishes, Factory stops every sandbox it holds, from any
Factory process, by identity through the configured sandbox provider.
Before, only the process that had opened a sandbox stopped it.
- A card that comes back to a context resumes the same sandbox with its
files.
Stopping never fails the move. Sandboxes are stopped, not destroyed;
deleting a session still destroys its sandbox.
- Added two read routes that answer what the new session page shows
without sending a project's cards.
([#30097](https://github.com/mastra-ai/mastra/pull/30097))
`GET /web/factory/projects/:id/work-items/starters` counts the cards
behind each starter on the project's default board, such as the cards
whose run failed, the pull requests awaiting review and the cards not
yet triaged.
`GET /web/factory/projects/:id/work-items/activity?since=<instant>`
returns how many cards the project has, and when cards were created and
completed since that instant. `since` is required and must be an ISO
date-time such as `2026-06-01T00:00:00.000Z`. The answer carries an
`ETag`, so asking again for the same `since` with `If-None-Match`
returns a 304 with no body when nothing changed.
### Patch Changes
- Fixed environment templates that could stop rebuilding for good. When
a build start was never recorded and the sandbox provider can't list its
builds (Mastra Platform), every later Build now, schedule and push run
used to skip with `unresolved` forever. Factory now treats that start as
failed 30 minutes after its lease lapsed and the next trigger builds.
([#30148](https://github.com/mastra-ai/mastra/pull/30148))
Saving a change to a template input (setup commands, the working
directory, settings, environment repositories, source-control
connections or Build variables) now rebuilds the template once the
project has one, so new sandboxes stop rerunning setup on every boot.
Saves that change nothing don't build, and a change saved during any
build, scheduled ones included, is built when that build ends.
- Factory sessions and MCP clients can now read the Factory's audit
trail with `factory_list_audit_events`: who did what to which work item,
run, branch or setting, and when. Filter by actor (`me`, a user id, or
an agent, optionally with the agent runs a person started), namespace or
exact actions, work item and time range, and page back with a cursor.
The tool only returns this Factory's events and never returns request
context (IP address, user agent), actor emails or event metadata beyond
who started an agent run. It leaves out events from or about other
people's private sessions.
([#30165](https://github.com/mastra-ai/mastra/pull/30165))
- Added a "Join the issue's card instead" switch to intake routes in the
Factory UI. A route for pull requests that close an issue can now put
the pull request on that issue's card instead of giving it a card of its
own; until now only the route Factory seeds could do this. The switch
shows on new and saved routes whose conditions include "Source kind is
Pull request" and "Pull request closes an issue is Yes".
([#30197](https://github.com/mastra-ai/mastra/pull/30197))
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/code-sdk@1.19.0-alpha.14
- @mastra/mcp@2.9.0-alpha.4
## @mastra/observability@1.24.0-alpha.7
### Minor Changes
- Add span-local error counts.
([#30088](https://github.com/mastra-ai/mastra/pull/30088))
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/core@1.83.0-alpha.12
### Minor Changes
- Add model and provider as span query sort fields.
([#30096](https://github.com/mastra-ai/mastra/pull/30096))
```ts
orderBy: [{ field: 'model', direction: 'asc' }];
```
- Add span-local error counts.
([#30088](https://github.com/mastra-ai/mastra/pull/30088))
### Patch Changes
- Name the agent in the missing-storage error thrown by `Memory`. When
an agent's memory never received storage because the agent was never
attached to a Mastra instance, accessing `memory.storage` now fails with
`[Agent:<name>] Memory requires a storage provider to function. ...`, so
it is clear which agent is misconfigured. The registration and
standalone-storage guidance added in #29972 is unchanged, and agents
that inherit storage from their Mastra or configure it directly on
`Memory` are unaffected.
([#30164](https://github.com/mastra-ai/mastra/pull/30164))
- Experiments with a scorer or processor target now save their scores,
and workflow step scorers in experiments now save their step scores.
Previously these scores were silently discarded.
([#30145](https://github.com/mastra-ai/mastra/pull/30145))
## @mastra/mcp-apps-components@0.1.0-alpha.7
### Minor Changes
- Dashboards authored in chat now accept the same widgets as the
dashboard editor: KPIs that combine values (ratio, difference, max,
fallback), read trace, span or score aggregates (for example p95 span
duration) and use duration, percent or score formats; line charts of
scores; six more chart colors (blue, orange, pink, yellow, red, purple);
and optional KPI icon and detail, series color and table empty message.
([#30192](https://github.com/mastra-ai/mastra/pull/30192))
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/playground-ui@69.0.0-alpha.14
### Minor Changes
- Widened what dashboard widgets can show:
([#30192](https://github.com/mastra-ai/mastra/pull/30192))
- KPIs can combine values with `ratio`, `minus`, `max` and `coalesce`,
read trace and span aggregates (for example `duration.p95`) and score
aggregates, and are formatted as `duration`, `percent` or `score`.
Combined values are compared with the previous window.
- Charts accept six more colors: `blue`, `orange`, `pink`, `yellow`,
`red` and `purple`.
- KPI `icon` and `detail`, series `color` and table `emptyMessage` are
optional. Series without a color pick one from a palette, and tables
without an empty message show "No data".
### Patch Changes
- Fixed hover highlights on cards and other surfaces stopping short of
the edge. The highlight now covers the whole surface and follows its
rounded corners exactly, including the sidebar credits card and
clickable cards. Hover highlights on these surfaces now switch instantly
instead of fading.
([#30047](https://github.com/mastra-ai/mastra/pull/30047))
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`987566e`](987566e882),
[`72abae6`](72abae68eb),
[`987566e`](987566e882),
[`f071044`](f0710446e0)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/client-js@1.60.0-alpha.12
- @mastra/react@1.15.0-alpha.12
## @mastra/server@1.83.0-alpha.12
### Minor Changes
- Support model and provider sorting in span queries.
([#30096](https://github.com/mastra-ai/mastra/pull/30096))
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/clickhouse@1.30.0-alpha.4
### Minor Changes
- Sort span queries by model or provider in ascending or descending
order. ([#30096](https://github.com/mastra-ai/mastra/pull/30096))
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/duckdb@1.19.0-alpha.5
### Minor Changes
- Sort span queries by model or provider in ascending or descending
order. ([#30096](https://github.com/mastra-ai/mastra/pull/30096))
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/pg@1.36.0-alpha.6
### Minor Changes
- Sort span queries by model or provider in ascending or descending
order. ([#30096](https://github.com/mastra-ai/mastra/pull/30096))
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/react@1.15.0-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`987566e`](987566e882),
[`72abae6`](72abae68eb),
[`987566e`](987566e882),
[`f071044`](f0710446e0)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/client-js@1.60.0-alpha.12
## @mastra/deployer-cloud@1.83.0-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/deployer@1.83.0-alpha.12
## @mastra/longmemeval@1.1.42-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/libsql@1.30.0-alpha.3
## @mastra/opencode@0.1.42-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/libsql@1.30.0-alpha.3
## create-factory@0.4.3-alpha.14
### Patch Changes
- Updated dependencies
[[`1fbc69a`](1fbc69aa9a),
[`4e378c3`](4e378c3e26),
[`1fbc69a`](1fbc69aa9a)]:
- mastra@1.39.0-alpha.14
## @mastra/code-sdk@1.19.0-alpha.14
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`987566e`](987566e882),
[`72abae6`](72abae68eb),
[`987566e`](987566e882),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
- @mastra/duckdb@1.19.0-alpha.5
- @mastra/client-js@1.60.0-alpha.12
- @mastra/pg@1.36.0-alpha.6
- @mastra/mcp@2.9.0-alpha.4
- @mastra/libsql@1.30.0-alpha.3
## mastracode@0.50.0-alpha.13
### Patch Changes
- Fix `/settings` crashing when mouse preferences are missing from saved
settings by defaulting to Off.
([#30184](https://github.com/mastra-ai/mastra/pull/30184))
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882),
[`f071044`](f0710446e0)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
- @mastra/duckdb@1.19.0-alpha.5
- @mastra/pg@1.36.0-alpha.6
- @mastra/code-sdk@1.19.0-alpha.14
- @mastra/mcp@2.9.0-alpha.4
- @mastra/libsql@1.30.0-alpha.3
## @mastra/arize@1.3.30-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/otel-exporter@1.5.2-alpha.7
## @mastra/arthur@0.4.30-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/otel-exporter@1.5.2-alpha.7
## @mastra/braintrust@1.3.27-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
## @mastra/datadog@1.4.22-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
## @mastra/deepeval@0.1.24-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
## @mastra/laminar@1.3.32-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
## @mastra/langfuse@1.6.6-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
- @mastra/otel-exporter@1.5.2-alpha.7
## @mastra/langsmith@1.4.3-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
## @mastra/otel-bridge@1.5.22-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
- @mastra/otel-exporter@1.5.2-alpha.7
## @mastra/otel-exporter@1.5.2-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
## @mastra/posthog@1.4.7-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
## @mastra/sentry@1.2.32-alpha.7
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`72abae6`](72abae68eb),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/observability@1.24.0-alpha.7
- @mastra/otel-exporter@1.5.2-alpha.7
## mastra@1.39.0-alpha.14
### Patch Changes
- Added `mastra api factory work-item starters` and `mastra api factory
work-item activity`. The first counts the cards behind each new-session
starter on a project's default board. The second lists when a project's
cards were created and completed since an instant:
([#30097](https://github.com/mastra-ai/mastra/pull/30097))
```bash
mastra api factory work-item starters <project-id>
mastra api factory work-item activity <project-id>
'{"since":"2026-06-01T00:00:00.000Z"}'
```
- Added a "Join the issue's card instead" switch to intake routes in the
Factory UI. A route for pull requests that close an issue can now put
the pull request on that issue's card instead of giving it a card of its
own; until now only the route Factory seeds could do this. The switch
shows on new and saved routes whose conditions include "Source kind is
Pull request" and "Pull request closes an issue is Yes".
([#30197](https://github.com/mastra-ai/mastra/pull/30197))
- Improved the Factory new session page on large boards. Its starters
and its activity band now load the counts and dates they show instead of
downloading every card of the project. They show the same content as
before. ([#30097](https://github.com/mastra-ai/mastra/pull/30097))
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/deployer@1.83.0-alpha.12
## @mastra/deployer@1.83.0-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
## @mastra/mcp-docs-server@1.3.13-alpha.16
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/elysia@0.1.23-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
## @mastra/express@1.5.27-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
## @mastra/fastify@1.5.27-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
## @mastra/hono@1.7.25-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
## @mastra/koa@1.7.27-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
## @mastra/nestjs@0.3.0-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
## @mastra/next@0.2.41-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
- @mastra/hono@1.7.25-alpha.12
## @mastra/tanstack-start@0.2.41-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/server@1.83.0-alpha.12
- @mastra/hono@1.7.25-alpha.12
## @mastra/voice-openai-realtime@0.14.9-alpha.2
### Patch Changes
- Use gpt-realtime-2.1-mini by default for OpenAI Realtime voice
connections instead of the retired
gpt-4o-mini-realtime-preview-2024-12-17 model.
([#30183](https://github.com/mastra-ai/mastra/pull/30183))
## @mastra/inngest@1.11.2-alpha.8
### Patch Changes
- Support span-local error counts in Inngest workflows.
([#30088](https://github.com/mastra-ai/mastra/pull/30088))
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
## @mastra/temporal@0.6.0-alpha.12
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`72abae6`](72abae68eb),
[`987566e`](987566e882)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/deployer@1.83.0-alpha.12
## create-mastra@1.39.0-alpha.14
## @internal/playground@1.39.0-alpha.14
### Patch Changes
- Updated dependencies
[[`56f654f`](56f654fc0d),
[`f071044`](f0710446e0),
[`987566e`](987566e882),
[`72abae6`](72abae68eb),
[`f9088d8`](f9088d8510),
[`987566e`](987566e882),
[`f071044`](f0710446e0),
[`43d1e9c`](43d1e9c16d)]:
- @mastra/core@1.83.0-alpha.12
- @mastra/client-js@1.60.0-alpha.12
- @mastra/playground-ui@69.0.0-alpha.14
- @mastra/react@1.15.0-alpha.12
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and publish to npm
yourself or [setup this action to publish
automatically](https://github.com/changesets/action#with-publishing). If
you're not ready to do a release yet, that's fine, whenever you add more
changesets to main, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
`main` is currently in **pre mode** so this branch has prereleases
rather than normal releases. If you want to exit prereleases, run
`changeset pre exit` on `main`.
⚠️⚠️⚠️⚠️⚠️⚠️
# Releases
> The changelog information of each package has been omitted from this
message, as the content exceeds the size limit.
## @mastra/slack@1.9.0-alpha.0
## @mastra/factory@0.28.0-alpha.3
## @mastra/code-sdk@1.19.0-alpha.3
## mastracode@0.50.0-alpha.3
## @mastra/observability@1.24.0-alpha.2
## @mastra/core@1.83.0-alpha.3
## @mastra/mcp-apps-components@0.1.0-alpha.3
## @mastra/playground-ui@69.0.0-alpha.4
## @mastra/server@1.83.0-alpha.3
## @mastra/server-adapters-test-suite@0.3.0-alpha.1
## @mastra/platform-workspace@1.13.0-alpha.0
## @mastra/auth-better-auth@1.1.11-alpha.1
## @mastra/client-js@1.60.0-alpha.3
## @mastra/react@1.15.0-alpha.3
## @mastra/deployer-cloud@1.83.0-alpha.3
## @mastra/longmemeval@1.1.42-alpha.3
## @mastra/opencode@0.1.42-alpha.3
## create-factory@0.4.3-alpha.3
## @mastra/arize@1.3.30-alpha.2
## @mastra/arthur@0.4.30-alpha.2
## @mastra/braintrust@1.3.27-alpha.2
## @mastra/datadog@1.4.22-alpha.2
## @mastra/deepeval@0.1.24-alpha.2
## @mastra/laminar@1.3.32-alpha.2
## @mastra/langfuse@1.6.6-alpha.2
## @mastra/langsmith@1.4.3-alpha.2
## @mastra/otel-bridge@1.5.22-alpha.2
## @mastra/otel-exporter@1.5.2-alpha.2
## @mastra/posthog@1.4.7-alpha.2
## @mastra/sentry@1.2.32-alpha.2
## @mastra/agent-builder@1.2.1-alpha.1
## mastra@1.39.0-alpha.3
## @mastra/connect@1.3.2-alpha.2
## @mastra/deployer@1.83.0-alpha.3
## @mastra/editor@0.17.1-alpha.2
## @mastra/fastembed@1.3.7-alpha.0
## @mastra/mcp-docs-server@1.3.13-alpha.6
## @mastra/memory@1.41.1-alpha.1
## @mastra/elysia@0.1.23-alpha.3
## @mastra/express@1.5.27-alpha.3
## @mastra/fastify@1.5.27-alpha.3
## @mastra/hono@1.7.25-alpha.3
## @mastra/koa@1.7.27-alpha.3
## @mastra/nestjs@0.3.0-alpha.3
## @mastra/next@0.2.41-alpha.3
## @mastra/tanstack-start@0.2.41-alpha.3
## @mastra/convex@1.8.1-alpha.0
## @mastra/pg@1.36.0-alpha.2
## @mastra/inngest@1.11.2-alpha.2
## @mastra/temporal@0.6.0-alpha.3
## create-mastra@1.39.0-alpha.3
## @internal/playground@1.39.0-alpha.3
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and publish to npm
yourself or [setup this action to publish
automatically](https://github.com/changesets/action#with-publishing). If
you're not ready to do a release yet, that's fine, whenever you add more
changesets to main, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
`main` is currently in **pre mode** so this branch has prereleases
rather than normal releases. If you want to exit prereleases, run
`changeset pre exit` on `main`.
⚠️⚠️⚠️⚠️⚠️⚠️
# Releases
> The changelog information of each package has been omitted from this
message, as the content exceeds the size limit.
## @mastra/client-js@1.60.0-alpha.0
## @mastra/react@1.15.0-alpha.0
## @mastra/factory@0.28.0-alpha.0
## @mastra/code-sdk@1.19.0-alpha.0
## mastra@1.39.0-alpha.0
## @mastra/core@1.83.0-alpha.0
## @mastra/mcp@2.9.0-alpha.0
## @mastra/mcp-apps-components@0.1.0-alpha.0
## @mastra/playground-ui@69.0.0-alpha.0
## @mastra/server@1.83.0-alpha.0
## @mastra/nestjs@0.3.0-alpha.0
## @mastra/clickhouse@1.30.0-alpha.0
## @mastra/duckdb@1.19.0-alpha.0
## @mastra/libsql@1.30.0-alpha.0
## @mastra/pg@1.36.0-alpha.0
## @mastra/temporal@0.6.0-alpha.0
## @mastra/auth-better-auth@1.1.11-alpha.0
## @mastra/deployer-cloud@1.83.0-alpha.0
## @mastra/deployer-cloudflare@1.2.42-alpha.0
## @mastra/deployer-netlify@1.2.42-alpha.0
## @mastra/deployer-sandbox@0.3.27-alpha.0
## @mastra/deployer-vercel@1.2.42-alpha.0
## @mastra/longmemeval@1.1.42-alpha.0
## @mastra/opencode@0.1.42-alpha.0
## create-factory@0.4.3-alpha.0
## mastracode@0.49.1-alpha.0
## @mastra/arize@1.3.30-alpha.0
## @mastra/arthur@0.4.30-alpha.0
## @mastra/braintrust@1.3.27-alpha.0
## @mastra/datadog@1.4.22-alpha.0
## @mastra/deepeval@0.1.24-alpha.0
## @mastra/laminar@1.3.32-alpha.0
## @mastra/langfuse@1.6.6-alpha.0
## @mastra/langsmith@1.4.3-alpha.0
## @mastra/observability@1.23.2-alpha.0
## @mastra/otel-bridge@1.5.22-alpha.0
## @mastra/otel-exporter@1.5.2-alpha.0
## @mastra/posthog@1.4.7-alpha.0
## @mastra/sentry@1.2.32-alpha.0
## @mastra/agent-builder@1.2.1-alpha.0
## @mastra/connect@1.3.2-alpha.0
## create-mastra@1.39.0-alpha.0
## @mastra/deployer@1.83.0-alpha.0
## @mastra/editor@0.17.1-alpha.0
## @mastra/mcp-docs-server@1.3.13-alpha.0
## @mastra/memory@1.41.1-alpha.0
## @mastra/rag@2.7.3-alpha.0
## @mastra/redis-streams@0.8.1-alpha.0
## @mastra/elysia@0.1.23-alpha.0
## @mastra/express@1.5.27-alpha.0
## @mastra/fastify@1.5.27-alpha.0
## @mastra/hono@1.7.25-alpha.0
## @mastra/koa@1.7.27-alpha.0
## @mastra/next@0.2.41-alpha.0
## @mastra/tanstack-start@0.2.41-alpha.0
## @mastra/spanner@1.11.2-alpha.0
## @mastra/turso@0.1.21-alpha.0
## @mastra/inngest@1.11.2-alpha.0
## @mastra/gcs@0.3.6-alpha.0
## @internal/playground@1.39.0-alpha.0
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and publish to npm
yourself or [setup this action to publish
automatically](https://github.com/changesets/action#with-publishing). If
you're not ready to do a release yet, that's fine, whenever you add more
changesets to main, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
`main` is currently in **pre mode** so this branch has prereleases
rather than normal releases. If you want to exit prereleases, run
`changeset pre exit` on `main`.
⚠️⚠️⚠️⚠️⚠️⚠️
# Releases
> The changelog information of each package has been omitted from this
message, as the content exceeds the size limit.
## @mastra/client-js@1.59.0-alpha.2
## @mastra/factory@0.27.0-alpha.2
## @mastra/code-sdk@1.18.0-alpha.2
## mastra@1.38.0-alpha.2
## @mastra/core@1.82.0-alpha.2
## @mastra/editor@0.17.0-alpha.2
## @mastra/server@1.82.0-alpha.2
## @mastra/clickhouse@1.29.0-alpha.1
## @mastra/duckdb@1.18.0-alpha.1
## @mastra/pg@1.35.0-alpha.2
## @mastra/platform-workspace@1.12.0-alpha.1
## @mastra/react@1.14.1-alpha.2
## @mastra/deployer-cloud@1.82.0-alpha.2
## @mastra/deployer-sandbox@0.3.26-alpha.1
## @mastra/longmemeval@1.1.41-alpha.2
## @mastra/opencode@0.1.41-alpha.2
## @mastra/parallel@0.1.5-alpha.0
## create-factory@0.4.2-alpha.2
## mastracode@0.49.0-alpha.2
## @mastra/arize@1.3.29-alpha.1
## @mastra/arthur@0.4.29-alpha.1
## @mastra/braintrust@1.3.26-alpha.1
## @mastra/datadog@1.4.21-alpha.1
## @mastra/deepeval@0.1.23-alpha.1
## @mastra/laminar@1.3.31-alpha.1
## @mastra/langfuse@1.6.5-alpha.1
## @mastra/langsmith@1.4.2-alpha.1
## @mastra/observability@1.23.1-alpha.1
## @mastra/otel-bridge@1.5.21-alpha.1
## @mastra/otel-exporter@1.5.1-alpha.1
## @mastra/posthog@1.4.6-alpha.1
## @mastra/sentry@1.2.31-alpha.2
## @mastra/agent-builder@1.1.33-alpha.2
## @mastra/deployer@1.82.0-alpha.2
## @mastra/mcp@2.8.0-alpha.1
## @mastra/mcp-docs-server@1.3.12-alpha.3
## @mastra/memory@1.41.0-alpha.2
## @mastra/playground-ui@68.0.0-alpha.2
## @mastra/rag@2.7.2-alpha.0
## @mastra/elysia@0.1.22-alpha.2
## @mastra/express@1.5.26-alpha.2
## @mastra/fastify@1.5.26-alpha.2
## @mastra/hono@1.7.24-alpha.2
## @mastra/koa@1.7.26-alpha.2
## @mastra/nestjs@0.2.41-alpha.2
## @mastra/next@0.2.40-alpha.2
## @mastra/tanstack-start@0.2.40-alpha.2
## @mastra/dsql@1.5.6-alpha.0
## @mastra/libsql@1.29.0-alpha.1
## @mastra/mongodb@1.26.0-alpha.1
## @mastra/mssql@1.11.1-alpha.0
## @mastra/mysql@0.16.0-alpha.2
## @mastra/oracledb@0.5.6-alpha.0
## @mastra/spanner@1.11.1-alpha.0
## @mastra/turso@0.1.20-alpha.1
## @mastra/voice-google@0.14.5-alpha.0
## @mastra/inngest@1.11.1-alpha.1
## @mastra/temporal@0.5.0-alpha.2
## @mastra/e2b@0.16.1-alpha.1
## create-mastra@1.38.0-alpha.2
## @internal/playground@1.38.0-alpha.2
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Description
Braintrust priced Mastra model spans from its own price list. So it
showed the wrong cost, or no cost for models it does not know. The
exporter now sends the provider's real charge as
`metrics.estimated_cost`, and Braintrust uses that value instead of its
price list.
- Only provider-reported costs above 0 are sent (OpenRouter
`usage.cost`, Vercel AI Gateway `gateway.cost`). A charge of 0 is
skipped, because AI Gateway reports 0 for bring-your-own-key calls.
- Mastra's own price estimates stay out of `metrics`, so Braintrust
still prices those spans itself.
- Added a "Cost tracking" section to the Braintrust integration guide
and the `BraintrustExporter` reference.
- Merge after #28955, which fixes#28844. Until then, a run that resumes
after a tool approval puts the whole run's charge on the resumed span,
and this change would show that number in Braintrust.
## Related Issue(s)
Fixes#28845
## Type of Change
- [x] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [x] I have made corresponding changes to the documentation (if
applicable)
- [x] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
Braintrust can now use a model provider’s reported charge when it
calculates span costs. This helps cost reports match the charge more
closely.
## Changes
- For model-generation spans, the exporter sets `metrics.estimated_cost`
only when the cost is a finite, positive USD amount from a provider.
- Zero charges and Mastra cost estimates are not written to this metric.
The full `costContext` remains in span metadata.
- Added tests for provider-reported costs, zero charges, and Mastra
estimates.
- Documented the cost-tracking behavior and added a patch changeset for
`@mastra/braintrust`.
Tests were added, but no test run results were provided.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Fills the `timeToFirstTokenMs` span column that #28389 added empty, and
lets trace, span and thread queries return, filter and sort by it. Time
to first token is the time from the start of the model call (the
`model_inference` span) to the first streamed chunk. Unlike
`timeToFirstChunkMs`, it leaves out the work Mastra does before calling
the model.
- The tracker measures the value once, on the `model_inference` span,
when its first chunk arrives, and copies that number up the agent's own
chain (`model_step`, `model_generation`, `agent_run`) as a
`timeToFirstTokenMs` attribute, first write wins, the same way
`completionStartTime` is copied. Each step takes its own inference's
value; the generation and agent run take the first step's.
- Span export reads the attribute. Storage fills the column from it and
drops the key from the attributes JSON. The Platform collector and the
store row mappers already carry the column, so no DDL changes.
- Durable agents (core and `@mastra/inngest`) carry the number through
loop state beside `completionStartTime`, so a fresh tracker on another
worker ends the generation and agent run with both.
- Core contract, ClickHouse, Postgres and DuckDB return, filter and sort
the field. Trace rows use the root span's value. Thread rows use the
first trace's root when it is an agent run. Empty values sort last.
Stores declare `trace-query-time-to-first-token` and `-sort`; the server
returns 501 when a store lacks them.
- A fallback model attempt opens its own `model_inference` span, named
after the model it calls, so its value and label are its own, and a
failed attempt's span ends with its error. Braintrust and LangSmith keep
the attribute out of span metadata.
- Client types regenerated, `useTraceQuery` keeps new traces in order
under the new sort, docs and changesets added. No Studio changes.
- Also fixes two gaps that already affected `timeToFirstChunkMs`:
durable abort and tripwire exits now keep the clocks on the ended spans,
and span aggregation gates the timing field instead of failing inside
the store.
- After a failed model call, in-process agents count the retry wait and
durable agents do not. One test marked expected-to-fail pins that
difference.
Rebased on `main` after #28389 merged.
## Related Issue(s)
N/A (OBS-722 follow-up)
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [x] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [x] I have made corresponding changes to the documentation (if
applicable)
- [x] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
🤖 Generated with [Claude Code](https://claude.com/claude-code)
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This change measures how long a model takes to send its first piece of a
response. Supported storage systems can return, filter, and sort by this
time, which helps teams find slow responses.
## Summary
- Records `timeToFirstTokenMs` from the start of a model inference to
its first streamed chunk. The value is added to inference spans and
propagated to related model-step, generation, and agent-run spans.
- Gives each fallback model attempt its own inference span and timing
value. Carries timing across durable agent steps, including resumed runs
and abort or tripwire exits.
- Adds `timeToFirstTokenMs` to trace, span, and thread query results and
predicates. Trace values use the root span. Thread values use the first
trace’s root agent span.
- Adds sorting by this field for trace and span queries in ClickHouse,
PostgreSQL, and DuckDB. Missing values sort last. The server returns
`501` when a store does not support a requested predicate or sort.
- Updates client types, `useTraceQuery`, documentation, storage
capability declarations, and changesets. Braintrust and LangSmith
exporters exclude the field from span metadata.
- Adds and updates tests across tracing, durable workflows, query
handling, and storage conformance. Test execution results were not
provided.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Enables `no-else-return: error` in the root Oxlint config and removes
186 redundant `else` branches across 111 source/test files. Existing
rule defaults are retained.
Reviewed every code diff for behavior preservation. An independent
TypeScript AST comparison confirms that changes are limited to removing
`else` after returning branches, with the same expressions, statement
order, return values, and `try`/`catch`/`finally` boundaries. All
181,158 identifier occurrences retain their bindings. The recorder
replay path keeps an explicit block: flattening it would shadow the
earlier request `body` with the response `body` and introduce a
temporal-dead-zone error.
Extends the existing monorepo optimized-dependency test to assert that a
raw TypeScript workspace package, including its enum and transitive
dependency, still executes in the production bundle.
Validation: the root rule-only scan passes on 15,273 files with zero
diagnostics; formatting and `git diff --check` pass. Schema
compatibility tests: 1,060 passed, 9 skipped. Recorder runtime tests: 21
passed. The core selection initially passed 3,513 tests; rerunning the
suites requiring local server/cache access passed 185 tests, with one
remaining cache-file assertion also reproduced on unchanged `main`.
Remaining validation limits: four asset-download cases cannot reach
`placehold.co`; the changed-file lint run reports six import-order
errors reproduced on unchanged files from `main`. Deployer unit tests
and the monorepo test could not run because this checkout lacks required
package dependencies (`fs-extra`/workspace links and `get-port`,
respectively). These limits are left visible for CI. No changeset is
included because this is a behavior-preserving lint cleanup.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This PR makes the code easier to read by removing `else` branches that
are not needed after a return. It also enables a rule that catches those
branches and adds a test for loading a raw TypeScript workspace package
in a production bundle.
## Summary
- Enables Oxlint’s `no-else-return` rule at error severity and removes
186 redundant `else` branches across 111 files.
- Extends the monorepo optimized-dependencies test to check a raw
TypeScript workspace package, its enum, and a transitive dependency.
- Updates the deployer’s transpile-package path pattern.
- In workflow event processing, a truthy branch index with no matching
child now falls through to publish a skipped-step end event. Previously,
this case published no event.
- Keeps the recorder replay block explicit to avoid request/response
`body` shadowing and a temporal-dead-zone error.
## Validation
Reported checks passed: the rule-only scan across 15,273 files,
formatting, `git diff --check`, schema compatibility tests (1,060
passed, 9 skipped), recorder runtime tests (21 passed), and an initial
core test selection (3,513 passed).
Some test limits remain. Four asset-download cases could not reach
`placehold.co`. Changed-file lint reported six import-order errors that
also occur on unchanged files from `main`. Deployer unit tests and the
monorepo test could not run because dependencies were unavailable. On
rerun, suites requiring local server/cache access had 185 passes; one
cache-file assertion also reproduced on unchanged `main`.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
`BraintrustExporter` overrode neither `_flush()` nor `_postShutdown()`,
so both fell through to the base no-ops. Every `span.log`, `span.end`
and `logger.logFeedback` only enqueues on Braintrust's background
logger, which sends on its own schedule, so `flush()` returned with
nothing sent and `shutdown()` wrote abort rows for open spans and
returned before they were sent. Processes that flush and exit (or
Lambdas that freeze) lost span ends, scores, and abort rows. The SDK's
`beforeExit` hook does not run on `process.exit()`.
- `_flush()` and `_postShutdown()` now await `flush()` on the logger the
exporter uses (the provided logger or the lazily created local one).
- When Mastra traces attach to an ambient `currentSpan()`, those rows go
through that span's SDK state, so the exporter also awaits
`span.flush()` on the latest ambient span Mastra attached to (falls back
to the package-level `flush()` for stand-ins without it). One slot is
enough: every span from one SDK copy shares the same background logger,
so this does not grow on long-running servers.
- Added optional `flush()` to the `BraintrustLogger` and
`BraintrustSpan` types.
- Tests hold the logger flush open and assert `flush()` / `shutdown()`
do not resolve until it is released, that abort rows are written before
the flush, and that the ambient external span is flushed. All four fail
on `main`.
Verified against the real Braintrust API (`braintrust` SDK 3.36.0, real
`openai/gpt-5-mini` tool-calling agent, one score, two spans left open),
process exits right after `shutdown()`, rows then read back with BTQL:
| case | before (`@mastra/braintrust` 1.3.19) | after |
| --- | --- | --- |
| local logger | 12/14 agent rows, **8/14 ended, score 0/1, abort rows
0/2**, 21 items still queued at exit | 14/14 rows, **14/14 ended, score
1/1, abort rows 2/2**, 0 queued |
| provided logger + run inside `logger.traced()` (external span) | 13/14
rows, **8/14 ended, score 0/1, abort rows 0/2**, 19 queued | 14/14,
**14/14 ended, score 1/1, abort rows 2/2**, 0 queued |
Part E of #26501. The other exporters are separate PRs.
## Related Issue(s)
Part E of #26501
## Type of Change
- [x] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [x] Test update
## Checklist
- [x] I have made corresponding changes to the documentation (if
applicable)
- [x] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
Braintrust can send trace data in the background, so some data could be
left unsent when Mastra finished. This change makes `flush()` and
`shutdown()` wait for that sending to finish, including for traces
attached to an external Braintrust span.
## Summary
- Add optional `flush()` methods to the `BraintrustLogger` and
`BraintrustSpan` interfaces.
- Flush the exporter’s provided or locally initialized logger during
`flush()` and shutdown.
- Track the latest ambient span used by the exporter. Flush it when it
has a `flush()` method; otherwise, use Braintrust’s package-level
`flush()`.
- Add a patch changeset for `@mastra/braintrust`.
The supplied change summary reports tests for flush and shutdown
ordering, abort-row handling, and ambient-span flushing. Test results
were not independently verified.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
A run started with `tracingOptions: { traceId, parentSpanId }` (for
example an LLM judge under the turn it scores) replaced the Langfuse
trace name, input, output, metadata, user and session of the run that
started the trace. This PR adds the opt-in
`tracingOptions.nestUnderParent` flag from the [proposal on the
issue](https://github.com/mastra-ai/mastra/issues/24825#issuecomment-5908969295),
so the caller can say "this run is a child of that span".
```ts
await judge.generate('Grade this answer', {
tracingOptions: { traceId: turn.traceId, parentSpanId: turn.spanId, nestUnderParent: true },
});
// or: tracingOptions: nestUnderRun(turn)
```
- `@mastra/core`: new `TracingOptions.nestUnderParent`, new
`nestedUnderParent` field on exported spans, and a `nestUnderRun()`
helper that builds the options from a previous run's result.
- `@mastra/observability`: the flag is honored only together with
`parentSpanId` (otherwise ignored with a debug log). It travels in the
run's trace state, so every span of the run is exported with
`nestedUnderParent: true`. The run's tags are dropped. `rebuildSpan()`
keeps the mark.
- `@mastra/langfuse`: spans of a nested run do not write
`langfuse.trace.*`, `user.id` or `session.id`. The skipped values stay
on the observation as `mastra.metadata.*`.
- `@mastra/braintrust`: a nested run links to its parent by id (same
mechanism as the resume path), so it works when another process exported
the parent.
- The default does not change. A run with `parentSpanId` and no flag
behaves as before, so runs under a foreign parent (OTel, HTTP span) keep
their trace summary.
- One difference from the proposal: a resumed run is **not** marked
nested here. Today the resumed run supplies the final reply as the
Langfuse trace output, and marking it nested would drop that. I left the
resume case to #23704.
- Not in this PR: Datadog, LangSmith, Sentry and PostHog (the "options
to explore" part of the proposal). They only inherit the tags rule.
- Verified with real OpenAI + real Langfuse, published packages vs this
branch:
| Scenario | Before | After |
| --- | --- | --- |
| Run alone | assistant | assistant |
| Judge after run, flag on | judge | assistant |
| Run under foreign parent, no flag | assistant | assistant |
| Foreign parent + judge, flag on | judge | assistant |
| Judge started inside a tool of the run, flag on | judge |
assistant-tool |
| Judge with its own tags, user and session, flag on | judge + judge's
user, session and tags | assistant + the run's own user, session and
tags |
| Judge after run, no flag | judge | judge (unchanged) |
| Judge through `nestUnderRun()` | n/a | assistant |
| Judge in another process, flag on | judge | assistant |
- Verified with real Braintrust, judge in another process: before, the
judge run had `span_parents: null` (a second top-level span) and its
tags were written; after, `span_parents` is the outer run's span id and
no tags are written.
## Related Issue(s)
Fixes#24825
## Type of Change
- [x] Bug fix (non-breaking change that fixes an issue)
- [x] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [x] I have made corresponding changes to the documentation (if
applicable)
- [x] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR lets a run join an existing trace as a child without changing
the trace details set by the run that started it. It also adds a helper
that builds the nesting options from a previous run.
## What changed
- Added the opt-in `tracingOptions.nestUnderParent` flag. The flag
applies when the run joins the requested trace under the requested
parent span; otherwise, Mastra clears the nested marker and logs a debug
message.
- Added `nestUnderRun()` to build tracing options from a previous run’s
trace and span IDs.
- Marked nested spans so exporters can distinguish them, omitted their
run tags, and preserved the marker when spans are rebuilt.
- Updated Langfuse to keep nested-run trace fields, metadata, user ID,
and session ID off the trace-level attributes.
- Updated Braintrust to link nested runs to the parent span, including
when another process exported the parent.
- Added server schema support and documentation for the new option.
When the flag is absent, existing behavior remains unchanged. Resumed
runs and exporters other than Langfuse and Braintrust are outside this
change.
## Verification
The change summary reports automated tests for Mastra tracing, span
rebuilding, Langfuse, Braintrust, the helper, and server schemas. It
also reports manual verification with OpenAI, Langfuse, and Braintrust.
Test commands and results were not provided.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Update 2026-10-06 (commits added on this branch; origin/main merged in
to clear the lockfile conflict)
Dependabot opened new alerts overnight (4 critical). This pass adds:
- braintrust ^3.24.0 -> ^3.36.0 in @mastra/braintrust. braintrust 3.27
pulled in simple-git 3.36.0, which has critical and high advisories
(GHSA-x6jw-m9v5-85vh, GHSA-v5rq-49vh-5v5c via @simple-git/argv-parser
1.1.1, GHSA-858h-whjf-mvg5, GHSA-g4wm-2vf7-vfgr). Those are only fixed
in simple-git 4. braintrust 3.36 no longer depends on simple-git, so
simple-git drops out of the lockfile. @mastra/braintrust only uses
initLogger and currentSpan.
- wrangler ^4.110.0 -> ^4.147.0 (devDependency of
@mastra/deployer-cloudflare, type-only import). This moves workerd
1.20260708.1 -> 1.20261001.1 on that chain (Aikido medium). workerd
1.20260714.1 is still there through the miniflare 4 devDependency in
stores/cloudflare and stores/cloudflare-d1.
- source-map-js 1.2.1 -> 1.2.2 (GHSA-68fv-2mgg-jv7q, high). Added the
floor `source-map-js@>=1.0.0 <1.2.2: 1.2.2` in the root and in 15 nested
pnpm workspaces (9 e2e projects, mastracode/web, otel-bridge agent-hub
and hono-multi, agent-builder, mcp and memory integration-tests).
postcss, css-tree, magicast and @tailwindcss/node all declare ^1.2.x. In
the customer-refund template, a plain npm lock refresh was enough (no
override).
- postcss-selector-parser: raised the existing floor from `>=7.1.0
<7.1.3: 7.1.3` to `>=7.1.0 <7.1.6: 7.1.6` (GHSA-rj75-hqrm-r3gf, medium).
- observability/_examples/otel-bridge/hono-multi: tsx catalog ^4.21.0 ->
^4.23.15. tsx 4.23 uses esbuild ~0.28, so esbuild 0.27.2 is gone (Aikido
high and low, fixed in 0.28.1).
- Changeset `.changeset/vanta-2026-10-06.md`: patch for
@mastra/braintrust.
Still not fixed (as of 2026-10-06)
- sprintf-js 1.0.3/1.1.3 (GHSA-hp3w-g68c-fv3c): no patched release.
- postcss-selector-parser 6.0.10/6.1.3: the fix is only in 7.1.6.
@tailwindcss/typography 0.5.20 pins 6.0.10 exactly, and cssnano
6/postcss-calc 9 use ^6.
- katex 0.16.47 (GHSA-238p-pmpm-9mq7, low): the fix is in 0.18.2.
mermaid 12.1.0 still declares ^0.16.47.
- http-cache-semantics: 4.3.0 is now older than 24h, but it still
doesn't touch the max-stale path, and the advisory still lists no
patched version.
- braces 3.0.3 has no new release.
- The rest of the deferred list below is unchanged.
---
Vanta remediation for 2026-10-05. The finding list was rebuilt from
GitHub Dependabot, OSV-scanner on every tracked lockfile, and Aikido
intel (full intel.aikido.dev feed re-pulled today). It is not a Vanta
export.
What changed
Package bumps
- probe-image-size ^7.2.3 -> ^7.4.0 in @mastra/memory
(GHSA-gjj5-9665-rwrc, high).
- verdaccio ^6.10.4 -> ^6.10.5 in the 9 e2e projects. That moves
@verdaccio/core to 8.3.2 and js-yaml 5.2.2 -> 5.4.1
(GHSA-r3ph-w7gj-g6xm, medium).
- smol-toml 1.8.0 -> 1.9.0 pin in @mastra/code-sdk.
Root lockfile refresh (no range changes)
- serialize-javascript 7.0.5 -> 7.1.2, shell-quote 1.10.0 -> 1.12.0, ws
7.5.11 -> 7.5.13, enhanced-resolve -> 5.26.0, fs-extra 11.3.5 -> 11.4.1,
@sinclair/typebox 0.27.8 -> 0.27.12, @zip.js/zip.js 2.8.26 -> 2.23.0,
memfs/@jsonjoy.com/fs-snapshot 4.57.2 -> 4.80.0, @vue/* 3.5.38 ->
3.5.43.
pnpm overrides, for parents that pin an exact vulnerable version. All
stay in the same major.
- modern-tar 0.7.7 (just-bash), smol-toml 1.9.0 (just-bash,
@blaxel/core, @react-grab/cli, modal), strnum 2.4.2 (fast-xml-parser
5.10.1), inline-style-parser 0.2.9 (style-to-object 1.0.11),
`@opentelemetry/configuration>yaml` 2.9.1 (sdk-node 0.221).
Nested lockfiles
- shell-quote floor raised from <1.10.0 to <1.11.0 in examples/agent,
examples/voice-agent and otel-bridge/agent-hub.
- yaml 2.9.0 -> 2.9.1 in e2e-tests/pkg-outputs, examples/durable-agents,
mastracode/web, packages/mcp/integration-tests and the customer-refund
template.
- next 16.3.6 -> 16.3.8 in packages/memory/integration-tests.
- customer-refund template: tinypool 2.1.0 -> 2.1.2 through an override
scoped to oxfmt. oxfmt 0.59 pins it exactly, and bumping oxfmt would
change the template's format check.
Not fixed here
- braces 3.0.3 (GHSA-vfj7-8cjw-p6xm) and http-cache-semantics 4.2.0
(GHSA-ch52-4w7c-c8xp): no patched release. http-cache-semantics 4.3.0 is
outside the advisory range, but it doesn't change the max-stale code
path, so bumping to it would only hide the alert.
- extract-zip 2.0.1: no patched release. It comes from the webdriverio
chain that #25855 removes.
- workerd 1.20260708/1.20260714 (Aikido medium): miniflare 4.x stops at
workerd 1.20260730. The fix needs miniflare 5, which is only published
as an alpha.
- Major-only: @ai-sdk/provider-utils 2.2.8 / ai 4.3.19 (AI SDK v4),
@opentelemetry/core 1.30.1, esbuild 0.18/0.25/0.27.0 (convex pins 0.27.0
exactly), js-yaml 3, brace-expansion 1/2, uuid 11, zod 3, pino 8/9,
undici 6, plus other Aikido lows.
- websocket-driver 0.7.5: Aikido says the fix is 0.8.x, but no 0.8 is
published on npm.
The changeset is a patch for @mastra/memory and @mastra/code-sdk.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR updates several dependencies that have security fixes. It also
adds version rules so nested projects use safer versions of related
packages.
## Changes
- Updates `probe-image-size` in `@mastra/memory` to `^7.4.0` and pins
`smol-toml` in `@mastra/code-sdk` to `1.9.0`.
- Updates Verdaccio to `^6.10.5` in nine end-to-end test projects.
- Raises `shell-quote` overrides to `1.11.0` and adds overrides for
transitive dependencies, including `yaml`, `source-map-js`,
`postcss-selector-parser`, `modern-tar`, `smol-toml`, `strnum`,
`inline-style-parser`, and `tinypool`.
- Updates `braintrust` to `^3.36.0`, `wrangler` to `^4.147.0`, and `tsx`
to `^4.23.15`.
- Adds patch changesets for `@mastra/memory`, `@mastra/code-sdk`, and
`@mastra/braintrust`. The changesets report no API changes.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->