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/auth-auth0@1.3.0-alpha.0
## @mastra/auth-clerk@1.4.0-alpha.0
## @mastra/auth-okta@0.3.0-alpha.0
## @mastra/auth-supabase@1.2.0-alpha.0
## @mastra/client-js@1.60.0-alpha.13
## @mastra/auth@1.2.0-alpha.0
## @mastra/core@1.83.0-alpha.13
## @mastra/playground-ui@69.0.0-alpha.15
## @mastra/rag@2.8.0-alpha.3
## @mastra/server@1.83.0-alpha.13
## @mastra/server-adapters-test-suite@0.3.0-alpha.5
## @mastra/auth-better-auth@1.1.11-alpha.2
## @mastra/auth-cloud@1.2.9-alpha.0
## @mastra/auth-neon@0.3.6-alpha.1
## @mastra/auth-workos@1.6.9-alpha.0
## @mastra/discord@1.3.4-alpha.0
## @mastra/react@1.15.0-alpha.13
## @mastra/deployer-cloud@1.83.0-alpha.13
## @mastra/deployer-cloudflare@1.2.42-alpha.3
## @mastra/deployer-netlify@1.2.42-alpha.1
## @mastra/deployer-sandbox@0.3.27-alpha.1
## @mastra/deployer-vercel@1.2.42-alpha.1
## @mastra/longmemeval@1.1.42-alpha.13
## @mastra/opencode@0.1.42-alpha.13
## @mastra/factory@0.28.0-alpha.15
## create-factory@0.4.3-alpha.15
## @mastra/code-sdk@1.19.0-alpha.15
## mastracode@0.50.0-alpha.14
## @mastra/agent-builder@1.2.1-alpha.5
## mastra@1.39.0-alpha.15
## @mastra/connect@1.4.0-alpha.6
## @mastra/deployer@1.83.0-alpha.13
## @mastra/editor@0.17.1-alpha.7
## @mastra/mcp@2.9.0-alpha.5
## @mastra/mcp-docs-server@1.3.13-alpha.17
## @mastra/memory@1.41.1-alpha.5
## @mastra/schema-compat@1.4.0-alpha.2
## @mastra/elysia@0.1.23-alpha.13
## @mastra/express@1.5.27-alpha.13
## @mastra/fastify@1.5.27-alpha.13
## @mastra/hono@1.7.25-alpha.13
## @mastra/koa@1.7.27-alpha.13
## @mastra/nestjs@0.3.0-alpha.13
## @mastra/next@0.2.41-alpha.13
## @mastra/tanstack-start@0.2.41-alpha.13
## @mastra/voice-google-gemini-live@0.14.19-alpha.2
## @mastra/voice-openai-realtime@0.14.9-alpha.3
## @mastra/voice-xai-realtime@0.2.18-alpha.2
## @mastra/inngest@1.11.2-alpha.9
## @mastra/temporal@0.6.0-alpha.13
## create-mastra@1.39.0-alpha.15
## @internal/playground@1.39.0-alpha.15
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Description
Adds four toolsets to the built-in MCP server at `/api/mcp`:
- `memory`: threads, messages, memory search, and Observational Memory.
`get_observations` can wait for pending Observational Memory work, for
example right after `call_agent`.
- `observability`: trace and span queries, logs, and trace trajectories.
- `observability_analytics`: `analyze_metrics`, `analyze_scores`, and
`analyze_feedback`, plus metric name and label lookups.
- `stored_agents`: list allowed models, and create, read, and update
stored agents.
With these, an MCP client such as Claude Code can create an agent, talk
to it, read what it remembered, and explain a slow trace.
### Behavior
- **On by default, shown only when supported.** Each toolset appears
only when the app has the matching capability (a memory-enabled agent,
an observability store that supports the queries, an editor for stored
agents). Apps that don't set `server.mcp.toolsets` get these tools on
upgrade, including write tools. Set `toolsets` to keep the previous set,
or `readOnly: true` to drop writes. The changeset says this.
- **Same checks as HTTP.** Every tool dispatches through its HTTP route,
so authentication, RBAC, FGA, thread ownership, and agent visibility
apply unchanged. No MCP caller gets more access than the same caller
over HTTP.
- **Observability isn't scoped per user.** Anyone with
`observability:read` sees all traces, as over HTTP. The docs show how to
leave those toolsets out.
- **Builder model policy.** When the agent builder restricts models,
`create_stored_agent` and `update_stored_agent` check the model the
agent runs (`provider` and `name`, in every conditional variant; other
keys on `model` are rejected), models named in `defaultOptions` such as
`structuredOutput.model`, enabled fallback models (`modelList`), memory
models, input and output processor models, and the defaults they fall
back to. Anything the policy can't check is rejected. The HTTP
stored-agent routes don't apply this check. Agents created or updated
over MCP are published immediately (`update_stored_agent` defaults
`autoPublish` to `true`).
- **Results fit MCP client limits.** `get_trace` returns light span
records with every span id, and `get_span` returns one span in full.
Long lists are cut to fit, with a note on how to get the rest, and a
single oversized item has its long values shortened (ids are never cut).
- **Errors.** Bad `analyze_*` and `list_metric_names` arguments return
400. A failed observability store lookup is retried on the next request
instead of hiding the observability tools until restart.
Stacked on #29930.
## Test plan
- `@mastra/server`: unit tests for the toolsets, capability detection,
result sizing, and schemas.
- Shared adapter suite (`builtin-mcp-toolsets-test-suite`) on Hono,
Express, Fastify, Koa, Elysia, and NestJS: memory ownership compared
with HTTP on the same request, read-only mode, analytics dispatch, and
argument errors. Hono also runs observability tests against in-memory,
LibSQL, and DuckDB stores.
- `@mastra/editor` integration tests for the builder model policy across
`model` (static and conditional), `defaultOptions`, fallback models,
memory, and processors. They need no provider API keys.
- Run end to end with two users over MCP and HTTP, and with Claude Code.
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
## Description
Lets MCP clients such as Claude Code sign in to the built-in `/api/mcp`
endpoint with OAuth instead of a pasted token. The endpoint tells
clients where to sign in (RFC 9728 protected-resource metadata) and can
reject tokens issued for a different API (audience check).
```ts
new Mastra({
server: {
auth: new MastraJwtAuth({
jwksUri: 'https://auth.example.com/.well-known/jwks.json',
issuer: 'https://auth.example.com/',
}),
mcp: { oauth: { resource: 'https://my-app.example.com/api/mcp' } },
},
});
```
### Behavior changes
**OAuth discovery for `/api/mcp`** (`@mastra/server`, every server
adapter including NestJS)
- When `server.auth` is set and the built-in MCP server is on, a `401`
from `/api/mcp` carries `WWW-Authenticate: Bearer
resource_metadata="…"`. `error="invalid_token"` is added only when a
token was sent (RFC 6750 §3).
- Metadata is served publicly at
`/.well-known/oauth-protected-resource/api/mcp` and
`/.well-known/oauth-protected-resource`, with `Cache-Control: no-store`.
- The document lists `resource`, `authorization_servers`, optional
`scopes_supported`, and `bearer_methods_supported: ['header']`. Without
`oauth.resource`, `resource` is derived from the request origin.
- The challenge, metadata routes and audience check apply only to
`/api/mcp`. Other routes are unaffected.
**Audience check** (`server.mcp.oauth.resource`)
- When set, the token audience must include this exact value, or the
request gets 401.
- An invalid value (non-URL, or a non-loopback `http://` URL) turns
discovery off and logs an error, but the audience check still runs
against it. Requests fail closed until the value is fixed.
- A provider that can't check audience (no `verifyAudience`, for example
`SimpleAuth` API keys) is accepted by default. The server logs a startup
warning on adapters built on `MastraServer`, not on NestJS.
- `requireAudience: true` (opt-in, only valid together with `resource`)
rejects those requests on `/api/mcp` with 401 `invalid_token`. Inside
`CompositeAuth`, only requests accepted by such providers are rejected.
Without `resource`, nothing changes.
**Config and provider hooks** (`@mastra/core`)
- New `server.mcp.oauth` config: `resource`, `requireAudience`,
`authorizationServers`, `scopesSupported`.
- Two new optional auth-provider methods:
- `getOAuthMetadata()` advertises the provider's authorization server.
- `verifyAudience()` checks the token audience.
- `CompositeAuth` combines the authorization servers of its providers.
It checks the audience with the provider that accepted the token, and
rejects when that provider can't be determined. The new
`getAuthenticatedProvider(user)` returns that provider.
**Providers**
| Provider | Advertises its authorization server | Checks audience
against `oauth.resource` |
|---|---|---|
| `MastraJwtAuth` | Yes, its `issuer` | Yes |
| Auth0 | Yes, the tenant | Yes |
| Clerk | Yes, the Frontend API | No |
| Okta | Yes, the issuer | No: Okta already enforces its own `audience`
(`OKTA_AUDIENCE`) |
| Supabase | Yes, `<url>/auth/v1` (requires Supabase's OAuth 2.1 server)
| No |
`MastraJwtAuth` gains `jwksUri` and `issuer` options
(`JWT_AUTH_JWKS_URI`, `JWT_AUTH_ISSUER`), so it can verify tokens signed
by an identity provider. JWKS keys are restricted to their key type, so
HMAC tokens forged with the public key are rejected.
**JWT subject as user id** (`@mastra/auth`, Auth0, Clerk)
- When a token has no `id` claim, the user's `id` is now set to `sub`.
Existing `id` claims are kept.
- Standard OIDC access tokens only carry `sub`. Before this change, RBAC
never loaded roles for these users, so every protected route returned
`403 Missing required permission`.
- Unless `mapUserToResourceId` is set, this also scopes data for these
users:
- **Owned records** (stored agents, skills, workspaces and other owned
records): each user sees their own records plus public ones. Admin
permissions keep the full list.
- **Tool-provider connections:** per-author connections move from the
shared `default` owner to the user's `sub`. Existing connections need
reconnecting, or set `mapUserToResourceId: () => 'default'` to keep the
old shared behavior.
- **Feedback:** recorded with `sub` as the user id.
- The changeset describes all of these effects.
**Test suite** (`@mastra/server-adapters-test-suite`)
- New `createBuiltinMCPOAuthTestSuite`.
- The package now has `@mastra/auth` and `jose` as peer dependencies.
Stacked on #29929.
## Test plan
- `packages/server`: `src/server/mcp/oauth.test.ts` and
`oauth-without-mcp.test.ts`. They cover metadata, the challenge format,
resource validation, failing closed on an invalid `resource`, and
discovery working without `@mastra/mcp` installed.
- `packages/auth` `jwt.test.ts`:
- JWKS and issuer validation
- string and array `aud`
- an algorithm-confusion token that is HS256-signed with the real RSA
public key PEM and must be rejected
- `sub` used as `id`
- `packages/core` `composite-auth.test.ts`: per-provider audience
delegation, rejection when the authenticating provider is unknown, and
`getAuthenticatedProvider`.
- `auth/auth0`, `auth/clerk`, `auth/okta`, `auth/supabase` unit tests.
- `createBuiltinMCPOAuthTestSuite` on Hono, Express, Fastify, Koa and
Elysia, plus the NestJS equivalent. It checks:
- the challenge, and fetching the advertised metadata URL
- audience accept and reject, including for an invalid `resource`
- `requireAudience`:
- `SimpleAuth` + `resource`: 200 by default, 401 in strict mode
- a JWT with a matching audience: 200 in strict mode
- a mixed `CompositeAuth`: only the API key is rejected
- RBAC with a token that carries only `sub`
- that a `sub`-only user can't list another user's private stored agent
- `tsc --noEmit` and `oxlint` on the touched packages, plus docs `pnpm
check` and Vale.
- Manual run end to end with Claude Code against a local identity
provider: discovery, client registration, PKCE login, and two users with
different roles.
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
Dynamic agent config callbacks now get the authenticated end user as an
optional `user` argument, so you can personalize an agent without
digging auth keys out of `requestContext` yourself. It works in any
`DynamicArgument` callback: instructions, model, tools, memory,
workspace, processors, scorers, and so on.
```ts
import { Agent } from '@mastra/core/agent';
const supportAgent = new Agent({
id: 'support-agent',
instructions: ({ user }) =>
user ? `You are helping ${user.name ?? user.id}.` : 'You are a helpful assistant.',
model: ({ user }) => (user?.role === 'admin' ? 'openai/gpt-5' : 'openai/gpt-5-mini'),
tools: ({ user }) => (user ? { accountTool, ...(user.role === 'admin' ? { adminTool } : {}) } : {}),
memory: ({ user }) => (user ? userMemory : undefined),
});
```
`user` always has the same `MastraUser` shape, no matter which auth
provider you use, and it's `undefined` for unauthenticated requests:
```ts
import type { MastraUser } from '@mastra/core/types';
// { id: string; name?: string; email?: string; avatarUrl?: string; role?: string }
```
The server auth middleware builds it through a new overridable
`toMastraUser()` on `MastraAuthProvider`. The default handles common
shapes (`id`/`sub`/`userId`, `name`, `email`, `avatarUrl`/`picture`,
`role`), and JWT, Cloud, Supabase, Neon and Better Auth ship overrides
for their user objects. Custom providers can map their own shape:
```ts
import { MastraAuthProvider } from '@mastra/core/server';
import type { MastraUser } from '@mastra/core/types';
class MyAuth extends MastraAuthProvider<MyUser> {
async authenticateToken(token: string) { /* ... */ }
async authorizeUser(user: MyUser) { return true; }
toMastraUser(user: MyUser): MastraUser {
return { id: user.accountId, name: user.profile.displayName, role: user.permissions.primaryRole };
}
}
```
Inline auth configs can pass `toMastraUser` too. If the provider user
has no role and an RBAC provider is configured, the primary RBAC role
fills it in, so `user.role` also works with WorkOS, Okta, Google and
Neon. The raw provider user is still available when you need
provider-specific fields, and the new context key is reserved, so
clients can't spoof it through the request body:
```ts
instructions: ({ requestContext }) => {
const rawUser = requestContext.get('mastra__user'); // provider-specific object, unchanged
// ...
},
```
Dynamic `vectorStore` resolvers on RAG tools get `user` as well:
```ts
createVectorQueryTool({
indexName: 'docs',
model: embedder,
vectorStore: ({ user }) => (user ? tenantStores.get(user.id)! : sharedStore),
});
```
Inside core, every place that invoked a `DynamicArgument` callback
inline now goes through a single `resolveDynamicArgument` helper, which
reads the user from `requestContext` at call time. This is non-breaking:
callbacks get an extra optional field, providers get a method with a
working default. Requests served through an `MCPServer` don't get `user`
yet, since MCP builds its own request context; that's documented.
Tested with unit tests for the helper, normalization and each provider
override, middleware tests (inline config, provider role, RBAC role,
CompositeAuth ordering, unauthenticated), regression tests for the
migrated call sites, and an end-to-end test where an agent behind a fake
auth provider gets personalized instructions. Core, server, rag and the
touched auth packages typecheck clean, and their suites pass.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
When a signed-in user makes a request, configuration callbacks can now
use a standard set of details about that user. When a workflow resumes,
it uses the new request’s user details instead of restoring them from
the earlier run.
## Summary
- Added optional `user` data to `DynamicArgument` callbacks and RAG
vector-store resolvers. Callbacks can also use `getRequestUser()` to
read the normalized user from request context.
- Added the `MastraUser` type and `toMastraUser()` normalization hooks
for auth providers and inline auth configs. The server stores the
normalized user in a reserved request-context key and uses the primary
RBAC role when the user has no role.
- Updated core dynamic configuration paths to use the shared resolver.
Added user support to agent scopes and migrated A2A memory resolution.
- Added `withoutLiveRequestKeys()` to remove live authentication and
authorization data from saved context during workflow resume, restart,
and time travel. Saved non-authentication context, such as tenant data,
remains available.
- Added documentation and changesets. Raised relevant `@mastra/core`
peer dependency minimums to 1.81.0. MCPServer requests do not receive
the normalized `user`.
## Validation
The author reports passing typechecks and test suites across core,
server, RAG, and several auth packages. The author also reports three
failing Inngest tests and earlier failures in evented workflow and
scheduler tests, which reportedly fail the same way on comparison
sources. These results are author-reported and have not been
independently verified.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: mastracode <284800079+mastra-platform[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
## @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/factory@0.28.0-alpha.6
## @mastra/code-sdk@1.19.0-alpha.6
## @mastra/playground-ui@69.0.0-alpha.7
## @mastra/client-js@1.60.0-alpha.6
## @mastra/react@1.15.0-alpha.6
## @mastra/deployer-cloud@1.83.0-alpha.6
## @mastra/longmemeval@1.1.42-alpha.6
## @mastra/opencode@0.1.42-alpha.6
## create-factory@0.4.3-alpha.6
## mastracode@0.50.0-alpha.6
## @mastra/agent-builder@1.2.1-alpha.3
## mastra@1.39.0-alpha.6
## @mastra/core@1.83.0-alpha.6
## @mastra/deployer@1.83.0-alpha.6
## @mastra/editor@0.17.1-alpha.4
## @mastra/mcp@2.9.0-alpha.3
## @mastra/mcp-docs-server@1.3.13-alpha.9
## @mastra/memory@1.41.1-alpha.3
## @mastra/rag@2.7.3-alpha.2
## @mastra/schema-compat@1.3.18-alpha.0
## @mastra/server@1.83.0-alpha.6
## @mastra/elysia@0.1.23-alpha.6
## @mastra/express@1.5.27-alpha.6
## @mastra/fastify@1.5.27-alpha.6
## @mastra/hono@1.7.25-alpha.6
## @mastra/koa@1.7.27-alpha.6
## @mastra/nestjs@0.3.0-alpha.6
## @mastra/next@0.2.41-alpha.6
## @mastra/server-adapters-test-suite@0.3.0-alpha.3
## @mastra/tanstack-start@0.2.41-alpha.6
## @mastra/upstash@1.6.1-alpha.0
## @mastra/vectorize@1.1.5-alpha.0
## @mastra/voice-google-gemini-live@0.14.19-alpha.0
## @mastra/voice-openai-realtime@0.14.9-alpha.0
## @mastra/voice-xai-realtime@0.2.18-alpha.0
## @mastra/inngest@1.11.2-alpha.4
## @mastra/temporal@0.6.0-alpha.6
## create-mastra@1.39.0-alpha.6
## @internal/playground@1.39.0-alpha.6
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/auth-studio@1.4.0-alpha.1
## @mastra/factory@0.28.0-alpha.5
## @mastra/mcp-apps-components@0.1.0-alpha.5
## @mastra/playground-ui@69.0.0-alpha.6
## @mastra/client-js@1.60.0-alpha.5
## @mastra/react@1.15.0-alpha.5
## @mastra/deployer-cloud@1.83.0-alpha.5
## @mastra/longmemeval@1.1.42-alpha.5
## @mastra/opencode@0.1.42-alpha.5
## create-factory@0.4.3-alpha.5
## @mastra/code-sdk@1.19.0-alpha.5
## mastracode@0.50.0-alpha.5
## @mastra/agent-builder@1.2.1-alpha.2
## mastra@1.39.0-alpha.5
## @mastra/core@1.83.0-alpha.5
## @mastra/deployer@1.83.0-alpha.5
## @mastra/editor@0.17.1-alpha.3
## @mastra/mcp@2.9.0-alpha.2
## @mastra/mcp-docs-server@1.3.13-alpha.8
## @mastra/memory@1.41.1-alpha.2
## @mastra/rag@2.7.3-alpha.1
## @mastra/server@1.83.0-alpha.5
## @mastra/elysia@0.1.23-alpha.5
## @mastra/express@1.5.27-alpha.5
## @mastra/fastify@1.5.27-alpha.5
## @mastra/hono@1.7.25-alpha.5
## @mastra/koa@1.7.27-alpha.5
## @mastra/nestjs@0.3.0-alpha.5
## @mastra/next@0.2.41-alpha.5
## @mastra/server-adapters-test-suite@0.3.0-alpha.2
## @mastra/tanstack-start@0.2.41-alpha.5
## @mastra/libsql@1.30.0-alpha.2
## @mastra/turso@0.1.21-alpha.2
## @mastra/inngest@1.11.2-alpha.3
## @mastra/temporal@0.6.0-alpha.5
## create-mastra@1.39.0-alpha.5
## @internal/playground@1.39.0-alpha.5
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The NestJS adapter only applied the global body limit (10 MB by default)
to JSON requests and ignored `route.maxBodySize`, so routes like
`/observability/traces/query` (256 KiB) accepted much larger bodies than
on the other adapters. Multipart already used the route limit.
The controller now checks the route limit before handing the body to the
handler, using Content-Length or the parsed size for chunked requests,
and returns 413.
Added a test that posts a 300 KiB body to the traces query route. It got
422 before the fix and 413 after. NestJS adapter tests (2960), tsc and
lint pass.
Fixes PLTFRM-3162
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
Some routes need a smaller request limit than the app-wide limit. This
change makes the NestJS adapter reject oversized JSON requests with
status 413 instead of passing them to the route handler.
## Changes
- Captures raw JSON request bytes and checks them against
`route.maxBodySize`.
- Adds tests for oversized and chunked JSON requests to
`/api/observability/traces/query`.
- Adds a patch changeset for `@mastra/nestjs`.
Test-run results were not provided.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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>
## Description
Server adapters now cancel the stream a route returned once the client
disconnects, including a client that left before the route handler
returned. For agents with resumable streams, that cancel is the only
signal that the HTTP observer left. Without it, NestJS returned 404 "Run
not found" from `/observe` after a dropped `untilIdle` stream, the same
failure #29636 fixed for Express.
| Adapter | Before |
|---|---|
| Koa | `datastream-response` never cancelled; both route types missed
an early drop |
| Fastify | missed an early drop |
| NestJS | never cancelled |
| Hono | an early drop left the body open |
| Elysia | `datastream-response` never cancelled |
Also in this PR:
- **Backpressure (not part of the cancellation bug).** Express, Koa,
Fastify, NestJS and Elysia now wait for a slow client instead of
buffering the whole stream in memory. This is the only change for
Express.
- The route abort signal now fires when the client left while earlier
middleware ran (Express, Koa, Fastify, NestJS, Elysia).
- The agent controller session stream and the empty background task
stream close right away if the request was already aborted.
- `@mastra/server/server-adapter` exports `cancelReaderOnResponseClose`
and `writeWithBackpressure` for custom adapters, documented in the
custom adapter guide along with `createStreamDisconnectTestSuite`.
## Related issue(s)
Fixes#29640Fixes#28480
Follow-up to #29636. Elysia durable-disconnect failures are tracked in
#29667.
## 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 linked the related issue(s) in the description above
- [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
When a client disconnects, the server now stops reading data that the
client cannot receive. When a client reads slowly, several adapters wait
before sending more data instead of buffering the whole stream.
## Summary
- Added shared helpers to cancel stream readers when a Node.js response
closes and to wait for socket capacity before writing.
- Updated Express, Koa, Fastify, and NestJS stream handlers to cancel on
disconnect and apply backpressure. Their request-context handling also
detects disconnects that occur before close listeners are attached.
- Updated Hono and Elysia stream handling to respond to aborts and
process stream data incrementally.
- Updated the agent-controller session stream and background-task stream
to close when their abort signal is already set.
- Added a shared real-HTTP test suite for disconnects, early
disconnects, normal completion, and slow clients, with adapter-specific
test setups. Added durable-disconnect test setups for Koa and NestJS.
- Updated custom adapter documentation with stream-cancellation and
backpressure helpers, plus guidance for running the disconnect test
suite.
- Hono returns `datastream-response` bodies unchanged and cancels an
unread body on request abort.
## Change size and checks
- **Files changed:** 35
- **Lines added / removed:** 1,278 / 264
- **CI, build, and test results:** not available
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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 adds `@mastra/mcp-apps-components`, a package of prebuilt MCP Apps
you can serve from any `MCPServer`, plus the server and client changes
they need to read data safely as the signed-in user. Each app has its
own entry point (no root barrel). The first one is a dashboard renderer:
a tool returns a dashboard definition and the host renders it as live
observability charts.
```ts
import { MCPServer } from '@mastra/mcp';
import { dashboardRendererApp } from '@mastra/mcp-apps-components/dashboard-renderer';
import { observabilityAppTools } from '@mastra/mcp-apps-components/observability-tools';
new MCPServer({
id: 'dashboard-mcp-server',
name: 'Dashboard MCP Server',
version: '1.0.0',
appResources: { 'ui://mastra/dashboard': dashboardRendererApp() },
tools: { showObservabilityDashboard, ...observabilityAppTools },
});
```
## How it works
**The app.** A single self-contained HTML page, inlined into the
package's JS so it survives deployer bundling (Vercel, Netlify,
Cloudflare) with no file reads at runtime. Its iframe never reaches the
network: it reads data with `callServerTool` over the host's existing
MCP connection, so no CSP or `baseUrl` setup is needed. It follows the
host's light/dark theme. Drilldowns continue the conversation when the
host supports `ui/message`; on hosts that also support
`ui/update-model-context`, the app passes the exact filters as
structured context and posts a short prompt, otherwise it spells the
filters out in the message.
**Typed observability tools.** `observabilityAppTools` is 11 app-only
tools, one per read-only observability route the dashboard uses
(trace/span/metric/score aggregates, breakdowns, time series,
percentiles, and score listing). Each takes the route's own input schema
and runs the route in-process through the new `invokeRoute()`.
**`invokeRoute()` (`@mastra/server/server-adapter`).** Runs a JSON
server route in-process as the caller, with the same validation, RBAC
permission and FGA checks its HTTP endpoint applies on every adapter,
and returns `{ status, body }`. It does not re-authenticate: when auth
is configured, the request context must carry the user Mastra server
auth resolved, or the call gets a 401. Non-JSON routes throw, and
HTTP-only handler params (`request`, `registeredTools`, `taskStore`,
`routePrefix`) are not supplied.
**Caller identity in MCP tools.** MCP tools served over HTTP now see the
caller Mastra server auth resolved (user, permissions, roles, resource,
organization) in their `requestContext`, on Hono, Express, Fastify, Koa,
Elysia and NestJS. The server attaches it to the MCP request under a
symbol key, so it can only come from the server, never from
client-supplied auth claims.
**Hiding app-only tools.** `MCPClient.listTools()`/`listToolsets()` hide
tools marked `_meta.ui.visibility: ['app']` from agents.
**Studio host.** Studio advertises the host capabilities it handles
(tool calls, messages, model context), passes its theme, routes app tool
calls to the requested tool in the MCP tool playground, and refuses app
calls to model-only tools. App model context is added to the next user
message only, as a clearly delimited block of untrusted app data, never
as system instructions.
## Try it
`examples/agent` has a `dashboard-agent`. In Studio, try "Show me agent
runs over the last 7 days as a line chart".
## Docs
- New reference page for `invokeRoute()`.
- New "Use prebuilt Mastra apps" section in the MCP connections guide.
## Testing
- `invokeRoute` unit tests (auth, permission, validation, handler
errors, non-JSON routes).
- Shared MCP transport suite case, run on every adapter, checking tools
see the server-resolved user and permissions and unauthenticated calls
get 401.
- `observability-tools` tests through a real Hono server with auth and
RBAC: MCP calls, Studio relay, permission denial, invalid input, and a
bundled-consumer test for the inlined HTML.
- Playground and playground-ui tests for the app viewer and model
context handling.
- Manual Studio run: dashboard renders live data and drilldown sends the
context block with the next message.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This PR adds ready-made MCP apps, including a dashboard that shows
observability data. It also lets Studio display these apps and pass
their context to chat as untrusted user content.
## What changed
- Added `@mastra/mcp-apps-components` with a dashboard renderer and
app-only observability tools. The tools invoke server routes in-process
and use the routes’ validation and authorization checks.
- Added `invokeRoute()` for in-process execution of eligible JSON
routes.
- Updated MCP server adapters to pass trusted, server-resolved caller
identity to MCP tools. MCP client discovery filters app-only tools from
agent-facing listings.
- Updated Studio and the playground to render MCP apps, relay app tool
calls, provide host capabilities, restrict tool calls and links, and
attach app context to the next chat message.
- Added a dashboard agent example and documentation for MCP Apps and
`invokeRoute()`.
## Validation
The author reports tests for route invocation, observability tools, MCP
transports across all six adapters, and playground app and chat
behavior. The author also reports a manual Studio check. These results
were not independently verified.
The author reports that the npm reservation for
`@mastra/mcp-apps-components` remained open and required an npm
organization admin before merge.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
Requires a nonblank `feedback.traceId` and `score.traceId` on the OSS
observability POST endpoints, with `spanId` still optional. Missing,
null, empty, whitespace-only, and span-only requests return 400 before
storage is called. The generated JavaScript client types now require the
trace ID too.
Previously accepted:
```ts
await client.createFeedback({ feedback: { feedbackType: 'thumbs', value: 1 } });
```
Now:
```ts
await client.createFeedback({
feedback: { traceId: 'trace-123', feedbackType: 'thumbs', value: 1 },
});
await client.createScore({
score: { traceId: 'trace-123', scorerId: 'accuracy', score: 0.9 },
});
```
This tightens the HTTP/type contract and uses minor changesets for core,
server, and client. Callers that previously omitted the trace ID must
now supply it. It does not add a trace-existence lookup or change
storage/batch APIs, historical nullable records, generated IDs, server
timestamps, or response shapes. The existing React feedback caller
already supplies a trace ID. Documentation describes the required trace
ID and optional span ID. Client types and CLI metadata were regenerated,
with no CLI metadata diff.
Validation: 398 tests pass, including shared real-HTTP regressions
across Hono, Express, Fastify, Koa, and NestJS, plus schema and existing
server/client tests. The new rejection cases failed before the fix with
200 responses. Focused client route-type checks, package builds,
type-aware lint, formatting, and documentation checks pass. The broader
client type suite still reports four errors in
`type-tests/trace-query.test-d.ts`; these were reproduced with the
unchanged main files.
Fixes
[OBS-788](https://linear.app/kepler-crm/issue/OBS-788/require-trace-ids-on-oss-score-and-feedback-posts).
Part of [OBS-792](https://linear.app/kepler-crm/issue/OBS-792); aligns
the required trace-ID contract with
[platform#3752](https://github.com/mastra-ai/platform/pull/3752).
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
Feedback and score requests must now identify the trace they belong to.
This prevents new requests without a usable trace ID from being saved,
while older records remain readable.
## Summary
- Require a nonblank `traceId` in feedback and score HTTP POST bodies.
Keep `spanId` optional.
- Reject requests with missing, null, empty, or whitespace-only
`traceId` values before calling storage.
- Keep nullable `traceId` values valid in storage and record schemas so
historical records remain readable.
- Update client request types, documentation, and the CLI score-create
example to include the required `traceId`.
- Add shared HTTP contract tests for the Hono, Express, Fastify, Koa,
and NestJS adapters.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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/factory@0.27.0-alpha.3
## @mastra/agent-builder@1.2.0-alpha.3
## @mastra/core@1.82.0-alpha.3
## @mastra/mcp@2.8.0-alpha.2
## @mastra/memory@1.41.0-alpha.3
## @mastra/playground-ui@68.0.0-alpha.3
## @mastra/ring-signals@0.1.0-alpha.0
## @mastra/libsql@1.29.0-alpha.2
## @mastra/mongodb@1.26.0-alpha.2
## @mastra/mysql@0.16.0-alpha.3
## @mastra/pg@1.35.0-alpha.3
## @mastra/discord@1.3.3-alpha.0
## @mastra/slack@1.8.1-alpha.0
## @mastra/teams@0.1.4-alpha.0
## @mastra/telegram@0.2.5-alpha.0
## @mastra/client-js@1.59.0-alpha.3
## @mastra/react@1.14.1-alpha.3
## @mastra/deployer-cloud@1.82.0-alpha.3
## @mastra/longmemeval@1.1.41-alpha.3
## @mastra/opencode@0.1.41-alpha.3
## create-factory@0.4.2-alpha.3
## @mastra/code-sdk@1.18.0-alpha.3
## mastracode@0.49.0-alpha.3
## @mastra/arize@1.3.29-alpha.2
## @mastra/arthur@0.4.29-alpha.2
## @mastra/laminar@1.3.31-alpha.2
## @mastra/langfuse@1.6.5-alpha.2
## @mastra/otel-bridge@1.5.21-alpha.2
## @mastra/otel-exporter@1.5.1-alpha.2
## @mastra/sentry@1.2.31-alpha.3
## mastra@1.38.0-alpha.3
## @mastra/connect@1.3.1-alpha.1
## @mastra/deployer@1.82.0-alpha.3
## @mastra/editor@0.17.0-alpha.3
## @mastra/evals@1.10.11-alpha.0
## @mastra/mcp-docs-server@1.3.12-alpha.4
## @mastra/server@1.82.0-alpha.3
## @mastra/elysia@0.1.22-alpha.3
## @mastra/express@1.5.26-alpha.3
## @mastra/fastify@1.5.26-alpha.3
## @mastra/hono@1.7.24-alpha.3
## @mastra/koa@1.7.26-alpha.3
## @mastra/nestjs@0.2.41-alpha.3
## @mastra/next@0.2.40-alpha.3
## @mastra/tanstack-start@0.2.40-alpha.3
## @mastra/turso@0.1.20-alpha.2
## @mastra/inngest@1.11.1-alpha.2
## @mastra/temporal@0.5.0-alpha.3
## create-mastra@1.38.0-alpha.3
## @internal/playground@1.38.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.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>
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.59.0-alpha.1
### Minor Changes
- Added the `aggregateTimeToFirstMeasures` observability capability.
Trace and span aggregate requests for `timeToFirstToken.*` or
`timeToFirstChunk.*` measures now return `501` against stores that can't
compute them, and field discovery omits those measures for such stores.
([#29055](https://github.com/mastra-ai/mastra/pull/29055))
```typescript
const { capabilities } = await
mastraClient.getObservabilityCapabilities();
if (capabilities.traceAggregate &&
capabilities.aggregateTimeToFirstMeasures) {
const { rows } = await mastraClient.aggregateTraces({
timeRange: { from: '2026-08-01T00:00:00.000Z', to:
'2026-08-02T00:00:00.000Z' },
groupBy: ['entityName'],
measures: ['timeToFirstChunk.p95', 'timeToFirstChunk.count'],
});
}
```
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/factory@0.27.0-alpha.1
### Minor Changes
- The same Jira, Linear or incident.io item can now be filed in more
than one Factory project. Before, the first project to file an item held
it for the whole org, and other projects that ingested it got no card.
Each project now keeps its own card. Within a project the card is still
reused when the item is seen again, after the card finishes and when the
issue reopens. A Linear card is also found after the issue's identifier
changes, for example when the issue moves to another team.
([#29059](https://github.com/mastra-ai/mastra/pull/29059))
When intake routing sends an item to a different project, the new
project files its own card and the previous project's card stays where
it is.
**Breaking changes**
- `claimKey` is removed from the `upsertLinkedWorkItem` decision type.
Rules that still return it, and decisions saved before this release,
keep working: the field is accepted and ignored.
- `WorkItemClaimConflictError`, `getByClaimKey`, `claimWorkItem`,
`releaseProjectClaims` and `WorkItemRow.claimKey` are removed.
Drop `claimKey` from linked-item decisions your rules return:
```ts
// Before
return {
type: 'upsertLinkedWorkItem',
source: 'jira-issue',
sourceKey: issue.id,
claimKey: `jira:issue:${issue.id}` /* … */,
};
// After
return { type: 'upsertLinkedWorkItem', source: 'jira-issue', sourceKey:
issue.id /* … */ };
```
Remove calls to `getByClaimKey`, `claimWorkItem` and
`releaseProjectClaims`. To find a project's card for an item, use
`getByProjectSource`.
The `claim_key` column stays in the database. Values already stored
there are left in place and no longer affect anything.
### Patch Changes
- Fixed shell commands that exit with a failure code reading as
successful in the Factory transcript. The command now reads as failed
while the run streams, after a dropped stream reconnects, and after a
reload. Stopping a process with `kill_process` still reads as a success.
([#28963](https://github.com/mastra-ai/mastra/pull/28963))
A system reminder that loads project instructions (`AGENTS.md`,
`CLAUDE.md` or `CONTEXT.md`) now reads "Project instructions" and names
the file by its path in the working directory, such as
`packages/core/AGENTS.md`, instead of a bare "System reminder".
- A board tool rule that moves a work item back into its current stage
with `reenter: true` now runs that stage's entry rules, as documented.
Previously the entry rules were skipped, so no new agent run started.
([#29104](https://github.com/mastra-ai/mastra/pull/29104))
- Updated dependencies
[[`5735a50`](5735a50c6c),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/platform-workspace@1.11.1-alpha.0
- @mastra/core@1.82.0-alpha.1
- @mastra/code-sdk@1.18.0-alpha.1
## @mastra/core@1.82.0-alpha.1
### Minor Changes
- Added time to first token and time to first chunk measures to trace
and span aggregates, so dashboards can chart streaming latency next to
duration. ([#29055](https://github.com/mastra-ai/mastra/pull/29055))
The new measures are `timeToFirstToken.avg`, `.min`, `.max`, `.p50`,
`.p90`, `.p95`, `.p99`, and `.count`, plus the same set for
`timeToFirstChunk`. Traces and spans without a recorded value are
skipped instead of counted as 0, and `.count` reports how many had one.
Stores opt in through the `aggregate-time-to-first-measures` feature.
### Patch Changes
- Fixed durable agents (`durable: true`) ending the `model_generation`
trace span without `responseId` and `responseModel`. Durable runs now
record the provider's response id and model on the span, the same as
non-durable agents, so a trace can be linked back to the provider's own
response log. Fixes#29053.
([#29180](https://github.com/mastra-ai/mastra/pull/29180))
- Fixed metadata filters in the in-memory store returning records whose
nested metadata had different keys from the filter when one side
contained an `undefined` value.
([#29101](https://github.com/mastra-ai/mastra/pull/29101))
- Fixed directly resumed nested workflows in the evented engine so they
continue suspended parent runs.
([#25979](https://github.com/mastra-ai/mastra/pull/25979))
## @mastra/playground-ui@68.0.0-alpha.1
### Minor Changes
- Toolbar and filter bar controls now share one look: the same paddings,
icon gaps, chevron and spacing between controls.
([#28818](https://github.com/mastra-ai/mastra/pull/28818))
**Time range.** A filter bar's time range is now the
`DateTimeRangePicker` itself, so it looks and behaves the same on every
page: a calendar icon, the range and a chevron, with no separate "Time"
label. Pass `defaultPreset` to show a × that resets a custom range; it
replaces the chevron while a custom range is applied.
Added `FilterBar.TimeRange` with `FILTER_BAR_TIME_RANGE_FIELD`,
`FILTER_BAR_TIME_RANGE_ITEM` and `FILTER_BAR_TIME_RANGE_FIELD_ID`. They
replace `TraceTimeRangeChip` and the `TRACE_TIME_RANGE_*` names from
`domains/traces/components/trace-time-range-chip`, which are removed.
```tsx
import {
FilterBar,
FILTER_BAR_TIME_RANGE_FIELD,
FILTER_BAR_TIME_RANGE_FIELD_ID,
FILTER_BAR_TIME_RANGE_ITEM,
} from '@mastra/playground-ui/components/FilterBar';
<FilterBar
fields={[FILTER_BAR_TIME_RANGE_FIELD, ...fields]}
operators={operators}
value={[FILTER_BAR_TIME_RANGE_ITEM, ...items]}
// The time range item is synthetic: keep it out of the stored filters.
onValueChange={next => setItems(next.filter(item => item.fieldId !==
FILTER_BAR_TIME_RANGE_FIELD_ID))}
>
<FilterBar.Chips
renderChip={item =>
item.fieldId === FILTER_BAR_TIME_RANGE_FIELD_ID ? (
<FilterBar.TimeRange
preset={preset}
// A preset, including the × reset, drops the applied custom dates.
onPresetChange={next => {
setPreset(next);
if (next !== 'custom') setRange({});
}}
dateFrom={range.from}
dateTo={range.to}
onDateRangeChange={(from, to) => setRange({ from, to })}
defaultPreset="last-7d"
/>
) : (
<FilterBar.Chip item={item} />
)
}
/>
<FilterBar.Input />
</FilterBar>;
```
`DateTimeRangePicker` gains `size`, `defaultPreset` and `ref` (the
trigger button).
**Migrating removed APIs.**
- `TraceTimeRangeChip` → `FilterBar.TimeRange` (same props), and
`TRACE_TIME_RANGE_FIELD` / `_ITEM` / `_FIELD_ID` →
`FILTER_BAR_TIME_RANGE_FIELD` / `_ITEM` / `_FIELD_ID`, imported from
`@mastra/playground-ui/components/FilterBar`.
```tsx
// Before
import { TraceTimeRangeChip, TRACE_TIME_RANGE_FIELD_ID } from
'@mastra/playground-ui/domains/traces/components/trace-time-range-chip';
item.fieldId === TRACE_TIME_RANGE_FIELD_ID ? <TraceTimeRangeChip
preset={preset} onPresetChange={setPreset} /> : …
// After
import { FilterBar, FILTER_BAR_TIME_RANGE_FIELD_ID } from
'@mastra/playground-ui/components/FilterBar';
item.fieldId === FILTER_BAR_TIME_RANGE_FIELD_ID ? <FilterBar.TimeRange
preset={preset} onPresetChange={setPreset} /> : …
```
- `DateTimeRangePicker`'s `renderTrigger` → remove it: the trigger is
always the shared calendar button. Pass `size` for another rung and
`ref` to reach the trigger.
- `comboboxStyles.chevron` on a hand-built trigger → `<ButtonChevron
size={size} />` from `@mastra/playground-ui/components/Button`.
**Other controls.**
- Added `ClearFiltersButton`, a round reset icon button with a tooltip,
used for every toolbar's "clear filters".
- Added `TriggerChevron` and `ButtonChevron`, the one chevron every
dropdown trigger (`Select`, `Combobox`, the date picker) shows.
- `ComboboxTrigger` uses that chevron instead of the up-down one.
- Icons in every interactive control (buttons, fields, search inputs,
filter chips, menu and command rows) follow one rule: muted at rest,
brighter on hover. Two new theme tokens, `--control-icon-rest` and
`--control-icon-hover`, set those colours; menus retune them, and
icon-only controls always brighten. Search fields and combobox fields
now brighten their icons on hover like buttons do.
- Icons take their size from the control they sit in, as in a Button:
filter chips and search inputs no longer size their own icons.
- `ListSearch` defaults to the `sm` toolbar size, and `SearchInput`'s
icon sits at the same inset as a button's.
- `ActionRow` and `FilterBar` space their controls 6px apart.
### Patch Changes
- Updated dependencies
[[`489d829`](489d8295c8),
[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`e1e64f0`](e1e64f072c),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/memory@1.41.0-alpha.1
- @mastra/client-js@1.59.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/ai-sdk@1.11.3
- @mastra/react@1.14.1-alpha.1
## @mastra/server@1.82.0-alpha.1
### Minor Changes
- Added the `aggregateTimeToFirstMeasures` observability capability.
Trace and span aggregate requests for `timeToFirstToken.*` or
`timeToFirstChunk.*` measures now return `501` against stores that can't
compute them, and field discovery omits those measures for such stores.
([#29055](https://github.com/mastra-ai/mastra/pull/29055))
```typescript
const { capabilities } = await
mastraClient.getObservabilityCapabilities();
if (capabilities.traceAggregate &&
capabilities.aggregateTimeToFirstMeasures) {
const { rows } = await mastraClient.aggregateTraces({
timeRange: { from: '2026-08-01T00:00:00.000Z', to:
'2026-08-02T00:00:00.000Z' },
groupBy: ['entityName'],
measures: ['timeToFirstChunk.p95', 'timeToFirstChunk.count'],
});
}
```
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/clickhouse@1.29.0-alpha.0
### Minor Changes
- Added support for `timeToFirstToken.*` and `timeToFirstChunk.*`
measures in trace and span aggregates. Rows without a recorded value are
skipped, never counted as 0.
([#29055](https://github.com/mastra-ai/mastra/pull/29055))
```typescript
import { planSpanAggregate } from '@mastra/core/storage';
const observability = await storage.getStore('observability');
if
(observability?.getFeatures().includes('aggregate-time-to-first-measures'))
{
const { rows } = await observability.aggregateSpans(
planSpanAggregate({
timeRange: { from: '2026-08-01T00:00:00.000Z', to:
'2026-08-02T00:00:00.000Z' },
where: { op: 'eq', left: { path: 'spanType' }, right: { literal:
'model_inference' } },
measures: ['timeToFirstToken.p50', 'timeToFirstToken.p95'],
}),
);
}
```
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/duckdb@1.18.0-alpha.0
### Minor Changes
- Added support for `timeToFirstToken.*` and `timeToFirstChunk.*`
measures in trace and span aggregates. Rows without a recorded value are
skipped, never counted as 0.
([#29055](https://github.com/mastra-ai/mastra/pull/29055))
```typescript
import { planSpanAggregate } from '@mastra/core/storage';
const observability = await storage.getStore('observability');
if
(observability?.getFeatures().includes('aggregate-time-to-first-measures'))
{
const { rows } = await observability.aggregateSpans(
planSpanAggregate({
timeRange: { from: '2026-08-01T00:00:00.000Z', to:
'2026-08-02T00:00:00.000Z' },
where: { op: 'eq', left: { path: 'spanType' }, right: { literal:
'model_inference' } },
measures: ['timeToFirstToken.p50', 'timeToFirstToken.p95'],
}),
);
}
```
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/pg@1.35.0-alpha.1
### Minor Changes
- Added support for `timeToFirstToken.*` and `timeToFirstChunk.*`
measures in trace and span aggregates. Rows without a recorded value are
skipped, never counted as 0.
([#29055](https://github.com/mastra-ai/mastra/pull/29055))
```typescript
import { planSpanAggregate } from '@mastra/core/storage';
const observability = await storage.getStore('observability');
if
(observability?.getFeatures().includes('aggregate-time-to-first-measures'))
{
const { rows } = await observability.aggregateSpans(
planSpanAggregate({
timeRange: { from: '2026-08-01T00:00:00.000Z', to:
'2026-08-02T00:00:00.000Z' },
where: { op: 'eq', left: { path: 'spanType' }, right: { literal:
'model_inference' } },
measures: ['timeToFirstToken.p50', 'timeToFirstToken.p95'],
}),
);
}
```
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/react@1.14.1-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/client-js@1.59.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/deployer-cloud@1.82.0-alpha.1
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
- @mastra/deployer@1.82.0-alpha.1
## @mastra/longmemeval@1.1.41-alpha.1
### Patch Changes
- Updated dependencies
[[`489d829`](489d8295c8),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`e1e64f0`](e1e64f072c),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/memory@1.41.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/libsql@1.29.0-alpha.0
## @mastra/opencode@0.1.41-alpha.1
### Patch Changes
- Updated dependencies
[[`489d829`](489d8295c8),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`e1e64f0`](e1e64f072c),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/memory@1.41.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/libsql@1.29.0-alpha.0
## create-factory@0.4.2-alpha.1
### Patch Changes
- Updated dependencies:
- mastra@1.38.0-alpha.1
## @mastra/code-sdk@1.18.0-alpha.1
### Patch Changes
- Updated dependencies
[[`489d829`](489d8295c8),
[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`e1e64f0`](e1e64f072c),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/memory@1.41.0-alpha.1
- @mastra/client-js@1.59.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/pg@1.35.0-alpha.1
- @mastra/duckdb@1.18.0-alpha.0
- @mastra/libsql@1.29.0-alpha.0
## mastracode@0.49.0-alpha.1
### Patch Changes
- Updated dependencies
[[`489d829`](489d8295c8),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`e1e64f0`](e1e64f072c),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/memory@1.41.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/pg@1.35.0-alpha.1
- @mastra/duckdb@1.18.0-alpha.0
- @mastra/code-sdk@1.18.0-alpha.1
- @mastra/libsql@1.29.0-alpha.0
## @mastra/sentry@1.2.31-alpha.1
### Patch Changes
- dependencies updates:
([#29123](https://github.com/mastra-ai/mastra/pull/29123))
- Updated dependency [`@sentry/node@^11.10.0`
↗︎](https://www.npmjs.com/package/@sentry/node/v/11.10.0) (from
`^10.76.2`, in `dependencies`)
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/agent-builder@1.1.33-alpha.1
### Patch Changes
- Updated dependencies
[[`489d829`](489d8295c8),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`e1e64f0`](e1e64f072c),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/memory@1.41.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## mastra@1.38.0-alpha.1
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
- @mastra/deployer@1.82.0-alpha.1
## @mastra/deployer@1.82.0-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/editor@0.16.7-alpha.1
### Patch Changes
- Updated dependencies
[[`489d829`](489d8295c8),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`e1e64f0`](e1e64f072c),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/memory@1.41.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/mcp-docs-server@1.3.12-alpha.2
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/memory@1.41.0-alpha.1
### Patch Changes
- dependencies updates:
([#29124](https://github.com/mastra-ai/mastra/pull/29124))
- Updated dependency [`diff@^9.0.0`
↗︎](https://www.npmjs.com/package/diff/v/9.0.0) (from `^8.0.4`, in
`dependencies`)
- Observational Memory now tells the Observer who sent each user signal.
In a thread shared by several people, messages sent with
`agent.sendMessage({ contents, attributes: { name: 'Alice' } }, ...)`
are labeled `User (name="Alice")` when observed, so observations can say
who said what instead of attributing everything to "User". Messages
without attributes keep the plain `User` label.
([#29176](https://github.com/mastra-ai/mastra/pull/29176))
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/google-cloud-pubsub@1.1.7-alpha.0
### Patch Changes
- dependencies updates:
([#29113](https://github.com/mastra-ai/mastra/pull/29113))
- Updated dependency [`@google-cloud/pubsub@^6.3.1`
↗︎](https://www.npmjs.com/package/@google-cloud/pubsub/v/6.3.1) (from
`^5.3.1`, in `dependencies`)
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/elysia@0.1.22-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/express@1.5.26-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/fastify@1.5.26-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/hono@1.7.24-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/koa@1.7.26-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/nestjs@0.2.41-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
## @mastra/next@0.2.40-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/hono@1.7.24-alpha.1
## @mastra/tanstack-start@0.2.40-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/server@1.82.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/hono@1.7.24-alpha.1
## @mastra/mysql@0.16.0-alpha.1
### Patch Changes
- Fixed experiment result writes putting plaintext back over a purged
dataset item. When a purge committed while a result was being written,
the writer could miss the purge marker and overwrite the redacted input,
output, ground truth, error and metadata.
([#29106](https://github.com/mastra-ai/mastra/pull/29106))
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/inngest@1.11.1-alpha.0
### Patch Changes
- Fixed `InngestRun.watch()` crashing the process with an unhandled
rejection when the Inngest realtime subscription fails to connect (for
example `fetch failed` or a WebSocket error). The failure is now logged
as a warning and the run still completes through polling. Unwatching now
also closes the realtime connection instead of leaving it open.
([#29103](https://github.com/mastra-ai/mastra/pull/29103))
- Fixed Inngest durable agents ending the `model_generation` trace span
without `responseId` and `responseModel`. The span now carries the
provider's response id and model, the same as non-durable agents. Fixes
#29053. ([#29180](https://github.com/mastra-ai/mastra/pull/29180))
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/temporal@0.5.0-alpha.1
### Patch Changes
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
- @mastra/deployer@1.82.0-alpha.1
## @mastra/e2b@0.16.1-alpha.0
### Patch Changes
- dependencies updates:
([#27993](https://github.com/mastra-ai/mastra/pull/27993))
- Updated dependency [`e2b@^2.62.0`
↗︎](https://www.npmjs.com/package/e2b/v/2.62.0) (from `^2.61.0`, in
`dependencies`)
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## @mastra/e2b-desktop@0.1.12-alpha.0
### Patch Changes
- dependencies updates:
([#27993](https://github.com/mastra-ai/mastra/pull/27993))
- Updated dependency [`e2b@^2.62.0`
↗︎](https://www.npmjs.com/package/e2b/v/2.62.0) (from `^2.61.0`, in
`dependencies`)
- Updated dependencies
[[`5735a50`](5735a50c6c),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/e2b@0.16.1-alpha.0
- @mastra/core@1.82.0-alpha.1
## @mastra/platform-workspace@1.11.1-alpha.0
### Patch Changes
- dependencies updates:
([#27993](https://github.com/mastra-ai/mastra/pull/27993))
- Updated dependency [`e2b@^2.62.0`
↗︎](https://www.npmjs.com/package/e2b/v/2.62.0) (from `^2.61.0`, in
`dependencies`)
- Updated dependencies
[[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/core@1.82.0-alpha.1
## create-mastra@1.38.0-alpha.1
## @internal/playground@1.38.0-alpha.1
### Patch Changes
- Updated dependencies
[[`0900c20`](0900c20592),
[`8751dd7`](8751dd7f56),
[`682e8f3`](682e8f3e44),
[`3314289`](33142896c1),
[`0900c20`](0900c20592),
[`ebf8a9a`](ebf8a9a137)]:
- @mastra/client-js@1.59.0-alpha.1
- @mastra/core@1.82.0-alpha.1
- @mastra/playground-ui@68.0.0-alpha.1
- @mastra/react@1.14.1-alpha.1
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Vanta 2026-10-30 security fixes (consolidated)
Direct dependency bumps and lockfile updates only. **No
overrides/resolutions added or raised.** The earlier override-based
edits on this branch were reverted; those findings are deferred below.
| Package | From → To | Advisory | Where |
|---|---|---|---|
| zod | ^3.25.76 → ^4.6.7 | zod <4.6.6 (High; no fixed 3.x) |
`client-sdks/react` (dev), `deployers/cloudflare` (dev),
`server-adapters/nestjs` (dev), `packages/editor` (dev),
`packages/playground-ui` (dep), `packages/playground`,
`workflows/_test-utils`, `examples/{durable-agents,inngest}`,
`explorations/longmemeval`,
`observability/_examples/otel-bridge/agent-hub`, e2e fixtures/templates
(`experiment-worker/fixtures/*`, `deployers/template/cloudflare`,
`no-bundling/template`, agent-builder `minimal-mastra-project`) + root
`pnpm-lock.yaml` |
| @hono/node-server | 1.19.x / 2.1.1 → 2.1.5 | CVE-2026-118663 /
GHSA-rmxm-3fg6-px4f (Medium) | direct deps: `examples/agent-builder`,
`otel-bridge/hono-multi/service-{one,two,mastra}`,
`templates/template-customer-refund-agent/client-demo-ui`,
`templates/template-kyc-customer-onboarding`,
`templates/template-security-incident-triage` |
Peer ranges (`^3.25.0 || ^4.0.0`) are unchanged, so consumers are
unaffected. Changeset: patch for `@mastra/playground-ui` (runtime zod
dep).
Supersedes the zod parts of #28075 (that PR also raises a pnpm override
and rewrites the `zod-v3` compat aliases to v4, so it is left as-is for
maintainers).
### Deferred (needs override, upstream release, or is intentional)
- zod v3 compat aliases (`zod-v3` in `packages/core`,
`packages/schema-compat`, `e2e-tests/type-check/template`;
`e2e-tests/client-js/zod-v3`): intentional zod 3 test coverage; no fixed
3.x release. Needs a decision to drop/dismiss.
- zod 3.25.76 transitive via `@arcadeai/arcadejs`, `@mcp-ui/client`,
firecrawl, `agent-browser`, `zod-to-json-schema`, MCP SDK paths:
upstream pins; override-only.
- @hono/node-server 1.19.x transitive via `@modelcontextprotocol/sdk`
(root, `examples/agent`, `packages/mcp/integration-tests`), and npm
lockfiles of `scripts/gh-issue-triage` (existing override, left alone)
and the two templates: override-only.
- graphql-scalars, raw-body, jose (templates/scripts): override-only.
- @azure/msal-node <7.1.0: 6.0.1 via `@azure/identity@4.14.0` (fixed in
4.14.1, blocked by the 1-day `minimumReleaseAge`; lockfile refresh
tomorrow), 5.6.0 via `@microsoft/teams.apps` (no fixed release).
- @opentelemetry/core <2.8.0: via `@google-cloud/pubsub@5` (fix needs
pubsub 6 major).
- @ai-sdk/provider-utils 2.2.8 / ai 4.x: pinned vendored AI SDK v4 line;
no fixed release in that major.
- extract-zip, deepmerge: no patched version.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This PR updates Zod and `@hono/node-server` versions in selected
packages, examples, and templates to address security advisories. It
also updates playground form code to work with Zod 4.
## Changes
- Updates selected `zod` dependencies to `^4.6.7`.
- Updates selected `@hono/node-server` dependencies to `2.1.5`.
- Updates the playground form’s IP address and record validators for Zod
4.
- Maps a specific Zod validation error to the message `Required`.
- Adds a patch changeset for `@mastra/playground-ui`.
## Validation
Test results are not provided in the supplied change summary.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: shreyas-mastra <327047572+shreyas-mastra@users.noreply.github.com>
**─────── TLDR ───────**
> Retries, memory, account rotation, the TUI and Factory now read a
failed model call through one reader in `@mastra/core/error`, so one
rule change fixes them all.
Follows #27811, which put this reader in Factory first. Before this PR,
seven hand-written status, code and wording tables disagreed. The retry
processor retried an exhausted quota, because the AI SDK marks every 429
retryable. Rotation only read quota wording on a 400. The run report
said `Bad Request`.
Now `classifyProviderError` reads the HTTP status, the provider codes,
the body and the wording, and every site asks it. Each site keeps only
the signals the reader can't see: a numeric `status`, network errors,
Retry-After and `ProviderAuthRequiredError`.
### Behavior changed
a 429 whose body says the quota is exhausted (`insufficient_quota`)
├─ **was** — retried, and the TUI says to wait a moment
└─ **now** — never retried; the TUI names the quota and
points to billing
a credential or usage failure named only in the provider's body
├─ **was** — no account rotation; Factory reports a plain
run failure
└─ **now** — rotates to the next account; Factory reports
bad credentials
a Factory run report for a failed provider call
├─ **was** — quotes the provider for usage limits only, else
`Bad Request`
└─ **now** — quotes the provider's own reason, cut at 400
characters
a mid-stream provider code, such as a Codex `server_error`, on the web
card
├─ **was** — `Run stopped`, live and after a reload
└─ **now** — named as an outage; the saved part keeps the
codes
a stream error that your own retry matcher and the built-in OpenAI
matcher both accept
├─ **was** — the built-in policy wins: one immediate retry,
no callback
└─ **now** — your matcher's `maxRetries`, `delayMs` and
`onRetry` apply
a tool's `EACCES: permission denied` ending a run
├─ **was** — the reader called it a provider credential
failure
└─ **now** — unknown; only the code form `permission_denied`
reads as auth
### Shape changed
| | | |
|---|---|---|
| **−** | `mastracode/factory/src/provider-error.ts` | its home in
#27811, back in core |
| **−** | memory `context-overflow.ts` | replaced by the reader's
`context_overflow` |
| **−** | `USAGE_LIMIT_MESSAGE_PATTERN` ×2 | rotation and run report
each kept a copy |
| **−** | `RETRYABLE_OPENAI_ERROR_CODES` ·
`TERMINAL_AUTHORIZATION_ERROR_CODES` | the reader's kinds |
| **+** | `quota` in code-sdk `ErrorType` | a quota can't be waited out
|
| **~** | `MastraErrorPart['error']` | keeps `codes` and the provider's
`reason` for a reload |
what callers now import from `@mastra/core/error`
`classifyProviderError(error)` ·
`providerErrorReason(error)` · `providerRequestId(error)` ·
`providerModelId(error)` · `toPersistedErrorIdentity(error)` ·
`PROVIDER_CALL_ERROR_NAME` · `type ProviderFailureKind`
### Decisions
- **overflow wording outranks a 5xx** — a gateway relaying `prompt is
too long` gets compacted, not retried; one rule in `provider-error.ts`
to drop.
- **a caller's numeric `status` outranks wording** — the reader ignores
`status`, which Octokit and MCP errors also carry, so rotation and
`parseError` read it first; a 503 saying `weekly limit` retries instead
of burning an account.
- **only a provider's own sentence is saved** — the saved `reason` comes
from an HTTP response or a stream frame, never from another error's
`detail`, which can name a database row.
### Not verified
- [ ] an app on `@mastra/core` 1.80.0-alpha.0 to alpha.4: the repo's
`-0` floor admits them and they predate the reader, as with `@mastra/pg`
on main; `check:core-imports` passes for server, memory and code-sdk
against this branch's core packed as 1.80.0
- [ ] `changed-tests` stays red: the deployer's core floor moves with no
monorepo E2E change, as on #28417
- [ ] account rotation against real provider accounts: the
`account-rotation`, `account-routing-targeted` and `pack-fallback` TUI
E2E pass with HTTP 429s through the real AI SDK, not a live account
- [ ] the web card after a reload with a real Codex `server_error`
frame: fixtures only
---
> ██████████████████ **source** `+304 −455` — net −151
> █████████████ **tests** `+399 −140`
> ███ **changeset** `+112`
> █ **package.json** `+20 −20` — core peer floor 1.80: server, memory,
agent-builder and editor import the reader
> █ **docs** `+10 −6`
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
Different parts of the project could interpret the same provider error
in different ways. This change gives them one shared reader so retries,
account rotation, saved errors, and user-facing reports handle those
errors more consistently.
## What changed
- Added provider-error classification and extraction helpers to
`@mastra/core/error`. They read provider codes, reasons, request IDs,
and model IDs from responses and wrapped errors.
- Updated retry handling, account rotation, observational-memory
context-overflow recovery, server error serialization, Factory reports,
and TUI error mapping to use the shared reader.
- Saved errors can include provider codes and reasons. Persisted
provider text is capped at 2,000 characters. Factory failed-run reports
use the provider reason when available and cap the report text at 400
characters.
- Configured retry matchers now run before built-in matchers. Built-in
retry handling excludes credential and exhausted-quota failures.
- Raised the minimum `@mastra/core` peer dependency to 1.80.0 across
affected packages and deployers.
## Verification and limitations
The supplied notes report that `check:core-imports` at the 1.80 floor is
unverified. They also report that `changed-tests` remains red after the
deployer core-floor change. Account rotation against real provider
accounts and web-card behavior after reloading a real Codex
`server_error` frame were not verified; unit tests and fixtures were
used instead.
Review finding counts are unavailable because no current review findings
were supplied.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
> Opened by @abhiaiyer91
## Summary
Running `tsc -p server-adapters/<adapter>/tsconfig.json` fails on `main`
for several adapters. Review gates that typecheck adapter packages fail
because of it.
**express, fastify, elysia:** each `examples/index.ts` destructures
`getInitData()` without a type argument. That call returns `unknown`, so
TS2339 fires. The fix passes a type argument, the same way
`server-adapters/hono/examples/index.ts` already does:
- `getInitData<typeof weatherWorkflow>()` for `city`
- `getInitData<{ vacationDescription: string }>()` for the travel
planner step. An inline type avoids a self-referential `typeof
travelAgentWorkflow`.
koa had the same error, but main fixed it in #28207. This PR takes
main's version and no longer changes koa.
**nestjs:** `tsdown.config.ts` set an `esbuildOptions` hook to force the
decorator compiler flags. The installed tsdown (0.23.1) builds with
rolldown and has no `esbuildOptions` option, so the hook never ran
during the build, and tsc rejects it (TS2769, TS7006). The decorator
flags already reach the build another way: `tsconfig.json` sets
`experimentalDecorators` and `emitDecoratorMetadata`, and tsdown passes
the tsconfig to rolldown. The fix deletes the dead hook and adds
`tsconfig: 'tsconfig.json'` so the source of those flags is explicit.
No `src/` or tsconfig changes, no ts-ignore, `any` or casts.
**No changeset, on purpose.** This PR only changes `examples/` and build
config, and no published output changes. Per the maintainer, it doesn't
get a changeset. The changeset gate check is expected to flag it.
## Proof
**tsc:** `npx tsc -p tsconfig.json --noEmit` from each adapter directory
(error counts). The After column is on head 3a5ef138, which has
origin/main 4d7ecb26 merged in.
| Adapter | Before (origin/main d7c7aedc) | After |
|---|---|---|
| hono | 0 | 0 |
| express | 2 (`examples/index.ts:206`, `:339`) | 0 |
| fastify | 1 (`examples/index.ts:217`) | 0 |
| koa | 1 (`examples/index.ts:202`), fixed on main by #28207 | 0 |
| elysia | 2 (`examples/index.ts:230`, `:378`) | 0 |
| nestjs | 2 (`tsdown.config.ts:13`, TS2769 and TS7006) | 0 |
| next | 0 | 0 |
| tanstack-start | 0 | 0 |
**nestjs dist:** I ran `pnpm build` in `server-adapters/nestjs` before
and after the config change. `diff -rq` across all 24 dist files (ESM,
CJS, `.d.ts` and sourcemaps) found no differences. The decorator
metadata output (`__decorateMetadata` / `design:paramtypes`) is present
in both builds.
**nestjs tests (`pnpm test`):** the same result before and after:
2838/2838 tests pass, and 16 of 19 test files pass. The other 3 files
(`auth-guard-export`, `malformed-json`, `mastra-module`) already fail on
main: vitest hits a parse error loading them and runs no tests from
them. vitest doesn't read `tsdown.config.ts`, so this PR can't affect
them.
**Lint:** `oxlint` and `oxfmt --check` on the changed files: clean.
## Unverified
- I didn't run the example servers. The examples change is type-only, so
the emitted JS is identical.
- I didn't fix or investigate the 3 nestjs test files that fail to load
on main.
- After the merge with main, I didn't rebuild nestjs or re-run its
tests. The merge didn't touch `tsdown.config.ts`.
Risk: low
---------
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>