0
Fork 0
mirror of https://github.com/mastra-ai/mastra.git synced 2026-11-17 08:44:46 +00:00
Commit graph

954 commits

Author SHA1 Message Date
dane-ai-mastra[bot]
d60ba71be0 chore: version - exit prerelease mode 2026-11-12 21:12:29 +00:00
dane-ai-mastra[bot]
5c87442ed7
chore: version packages (alpha) (#30203)
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>
2026-11-12 12:07:03 -08:00
Daniel Lew
18168d518c
feat(playground): show the built-in MCP server in Studio (#29932)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-12 13:40:02 -05:00
Daniel Lew
4ba2bdef89
feat(server): memory, observability and agent builder MCP toolsets (#29931)
## 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>
2026-11-12 10:25:19 -08:00
Daniel Lew
27705673f2
feat(server): OAuth discovery and audience checks for the built-in MCP endpoint (#29930)
## 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>
2026-11-12 10:10:31 -08:00
Daniel Lew
392c7b69d5
feat(server): built-in MCP endpoint for agents, workflows and tools (#29929)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-12 12:56:28 -05:00
Daniel Lew
d05afc4a90
refactor(server): shared route authorization and in-process dispatchRoute across adapters (#29928)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-12 12:30:28 -05:00
arctic-char
c0d3bfdc43
feat: pass the authenticated user to DynamicArgument callbacks (#28612)
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>
2026-11-12 10:55:12 -05:00
dane-ai-mastra[bot]
05a6931471
chore: version packages (alpha) (#30172)
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>
2026-11-12 14:42:02 +01:00
dane-ai-mastra[bot]
a4258a989c
chore: version packages (alpha) (#30127)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-11-11 21:12:19 -08:00
dane-ai-mastra[bot]
055a8c3b82 chore: version packages 2026-11-12 04:17:40 +00:00
dane-ai-mastra[bot]
9e82af0237
chore: version packages (alpha) (#30074)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-11-11 14:21:14 -08:00
mastra-platform[bot]
b0ef22e7bf
feat(schedules): Add bounded one-off schedules (#25131)
> Opened by @abhiaiyer91

Refs #24610

## Summary
Schedules can now fire once or stop after a given time, so you no longer
need to pin a cron expression to a date and clean it up yourself.

- **New `completed` status**: the scheduler and timing reconciliation
set it when no automatic fires remain. It's written in the same atomic
`nextFireAt` check-and-set used to claim a run, so a schedule still
fires only once across instances. A cron with no future occurrence left
also moves to `completed` instead of erroring. `pause`/`resume` on a
completed schedule return 409. Changing `runAt`/`endAt` reactivates it
only when the resulting timing can still fire. `list()` hides completed
schedules unless you pass `status: 'completed'`.
- **Declarative workflow schedules**: `createWorkflow({ schedule: {
runAt } })` and `{ cron, endAt }` are supported. Past times are accepted
so redeploys don't fail, and a completed schedule isn't re-armed unless
its timing changes.
- **Trigger kind**: one-off fires report `trigger.kind: 'once'`.
- `run(id)` doesn't complete a one-off schedule.

## Surfaces
- **Core**: types, validation, scheduler claim logic,
create/update/pause/resume/list, declarative sync.
- **Storage**: new nullable `run_at`/`end_at` columns for libsql, pg,
mysql, mongodb, spanner, convex and in-memory. Existing columns are
untouched: one-off schedules store `cron` as `''`.
`updateScheduleNextFire` takes an optional `newStatus`.
- **Server/client-js/CLI**: request bodies accept `runAt`/`endAt`
(one-of rule checked in the schema). Responses include the new fields
and `completed`. Route types and CLI route metadata regenerated.
- **Studio**: shows the run time for one-off schedules, shows the
`endAt` bound, adds a `completed` badge and hides pause/resume for
completed schedules.
- **Docs + changeset.**

## Not in this PR (remaining #24610 work)
- ISO 8601 string inputs for `runAt`/`endAt` (numbers and `Date` are
accepted today).
- The template `schedule_once` tool.

## Test plan
- [x] core: schedules, scheduler, cron, schedule-config and scheduler
integration tests (260 passing), clean `tsc`
- [x] Shared adapter suite gained tests for `runAt`/`endAt` round-trip
and atomic status CAS. Passing on libsql, pg, mysql and mongodb
(Docker), plus convex server tests. **Not run on Spanner (no emulator
available); typecheck only.**
- [x] server schedules handler tests (51 passing, including
one-off/bounded creation and body validation)
- [x] client-js and playground typecheck clean; playground schedules
tests passing

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

Schedules can now run once at a chosen time or repeat until a chosen end
time. They complete when their planned runs are over, and changing their
timing can make them active again.

## Summary

- Added `runAt` for one-off agent and workflow schedules. API-created
schedules require a future `runAt`; declarative workflow schedules can
register past times as `completed`.
- Added `endAt` for cron schedules. A schedule becomes `completed` when
its next run would occur after `endAt`, or when no future run remains.
- Completed schedules cannot be paused or resumed. Timing changes can
reactivate a completed schedule when a future run remains. `list()`
hides completed schedules unless callers filter with `status:
'completed'`.
- Resuming a paused one-off schedule after its `runAt` has passed allows
it to fire on the next scheduler tick. Calling `run(id)` manually does
not complete a one-off schedule.
- Added the `once` trigger kind for scheduled one-off agent fires.
Manual runs remain `manual`.
- Declarative workflow schedules preserve completed status across
redeploys when timing is unchanged. Timing changes can re-arm them.
- Updated schedule APIs, storage adapters, Studio, and documentation.
Storage persists `runAt` and `endAt` and supports atomic status updates.

## Checks

Current-head CI, build, and test results: not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Abhi Aiyer <abhiaiyer91@gmail.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: NikAiyer <nick.aiyer@gmail.com>
Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: Ehindero Israel <iehindero419@stu.ui.edu.ng>
2026-11-11 19:33:50 +01:00
Eric Pinzur
2053c881ed
fix(observability): export feedback review-status updates (#30075)
HTTP feedback review-status changes persist locally but do not reach
exporters. This forwards successful updates to supporting exporters and
adds `observability.updateFeedbackReviewStatus({ feedbackId,
reviewStatus })` for independent SDK delivery. A missing or slow local
record does not block remote delivery; the HTTP route still requires an
existing local record, honors the configured resourceId, and returns its
updated value. Organization IDs remain metadata and do not scope this
PATCH route.

MastraPlatformExporter sends the existing review-status PATCH contract,
retries recognized missing-feedback and temporary lookup responses, and
tracks delivery through flush/shutdown. Replacement PUTs and review
PATCHes for the same feedback ID share one queue through retries,
including failure recovery. This orders requests from one exporter
instance; successful publication still does not guarantee that a
subsequent PATCH reads the latest queued PUT from Platform storage.
Storage exporters wait for earlier creates of that feedback to resolve
and persist before updating it, including buffered and in-flight writes.
Other exporters remain independent. Optional hooks let older exporters
skip the update safely; HTTP updates still work when observability lacks
the notification hook. This covers review status only, with no general
PATCH or UI changes.

Fixes #24054, completing its remaining review-status exporter gap after
the create/replacement work. Part of OBS-785. Platform delivery requires
the matching endpoint from merged mastra-ai/platform#4651 to be
deployed; the Platform UI rollout remains separate.

Validation: the HTTP export regressions failed before the fix and pass
afterward. Shared HTTP suites pass in Hono, Express, Fastify, NestJS and
Koa (92 tests each); exporter HTTP tests (163 in the latest run) and
neighboring observability tests (234), and server handler tests (167)
pass. The retry-ordering, buffered-create, and inherited-hook
regressions failed before their fixes. Timing-sensitive ordering tests
passed 20 repeated runs, including PUT/PATCH in both directions with
flush/shutdown and independent IDs. Relevant builds, client-js build,
typed lint, formatting and docs checks pass. Route metadata regeneration
produces no diff. Local validation used Node 23.11.0, outside the
repository's supported engine range. Docs checks and CI-equivalent Vale
lint pass with Vale 3.25.1 installed.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

This PR sends feedback review-status changes to observability exporters,
not only local storage. It also adds an SDK method for sending these
updates directly.

## Summary

- Added `observability.updateFeedbackReviewStatus({ feedbackId,
reviewStatus })`.
- Added the `feedback_review_status` event and exporter hooks.
- Updated the HTTP route to validate local feedback and `resourceId`,
update local storage, return the updated record, and notify exporters.
- Added Platform `PATCH` delivery with retries for recognized
missing-feedback and temporary lookup responses.
- Serialized updates for the same feedback ID while keeping different
IDs independent.
- Allowed remote delivery when local feedback is missing or local
storage lacks review-status support.
- Preserved compatibility with exporters that do not implement the new
hook.
- Tracked pending updates through `flush()` and shutdown.
- Added documentation, changesets, and regression tests.
- Scope remains limited to review-status updates. No general `PATCH`
behavior or UI changes.

## Validation

- 21 files changed: 752 additions and 50 deletions.
- Reported HTTP suites passed for Hono, Express, Fastify, NestJS, and
Koa, with 92 tests per suite.
- Reported exporter HTTP tests, neighboring observability tests, and
server handler tests passed.
- Reported builds, client-js build, typed lint, formatting,
documentation checks, and route metadata checks passed.
- Vale validation used version 3.25.1.
- Validation used Node 23.11.0, outside the repository’s supported
engine range.
- Platform delivery requires deployment of the matching endpoint from
`mastra-ai/platform#4651`.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-11 19:08:11 +01:00
dane-ai-mastra[bot]
3a6ca42696
chore: version packages (alpha) (#30026)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-11-11 08:16:57 -08:00
Eric Pinzur
c860b9bb43
feat(observability): support OSS feedback replacement (OBS-887) (#30059)
Implements
[OBS-887](https://linear.app/kepler-crm/issue/OBS-887/add-oss-feedback-replacement-and-export).

Add OSS `PUT /api/observability/feedback/:feedbackId` with the existing
wrapped client request. Replacements retain the original feedback ID,
trace ID, timestamp, and tenant; omitted optional fields are cleared. A
full replacement can create a missing record. OSS persists locally
before responding, then independently notifies supporting exporters.
Resolve mode still requires the local anchor. The SDK also exposes
optional `replaceFeedback()` for independent exporter delivery without a
producer-side storage lookup.

Replacement events use a separate optional exporter hook.
`MastraPlatformExporter` sends PUT with stable identity across bounded
anchor retries, and flush/shutdown drain deliveries. Older exporters
skip replacements rather than replaying them as creates. Unsupported
storage/package combinations return 501 or skip unavailable export
support. No UI changes; review-status PATCH propagation remains tracked
in OBS-785.

In-memory, PostgreSQL vNext, DuckDB, and ClickHouse vNext support
replacement. In-memory, PostgreSQL, and DuckDB enforce replacement
identity at the write. PostgreSQL coordinates writes by feedback ID,
including duplicates submitted with a different timestamp. Duplicate
HTTP creates return the stored identity and timestamp and re-notify
exporters with accepted values. Tenant mismatches remain hidden, and an
omitted SDK replacement author stays null. HTTP/exporter creates use
`onConflict: 'ignore'` so a delayed original create doesn't undo an
edit; direct storage calls keep their legacy upsert default.
**ClickHouse requires no migration:** it uses the existing schema and
read-before-insert protection. Sequential delayed creates are covered,
but overlapping writes from separate processes can race; this is not a
globally ordered or exactly-once protocol.

Latest review fixes: DuckDB's lazy facade delegates replacement to its
guarded writer; concurrent coverage runs 20 overlapping request pairs
per identity variant. Direct storage replacements normalize an omitted
author to null. PostgreSQL single-feedback reads use the primary for
read-after-write consistency, while list/aggregate reads retain the
configured read client. Batch advisory locks use one ordered query with
unchanged lock keys.

Validation: the stronger DuckDB regression failed on all four identity
variants before the facade fix. Afterward, the entire DuckDB package
passed 718 tests across 21 files in three consecutive runs. PostgreSQL
passed 57 feedback tests, including a real stale read snapshot and
overlapping reversed 1,000-ID batches. Shared replacement tests passed
on in-memory (12), and the new author regression passed on ClickHouse
without a migration. Core/storage builds and declarations, typed lint,
and formatting passed. Earlier HTTP (85 cases on each of four adapters),
generic Hono routes (2,848), server/system, exporter, and docs checks
remain recorded in the PR history. Local tests use Node 23.11.0; CI
validates the supported runtime.

The unrelated Traces UI fade assertion failure was fixed in
https://github.com/mastra-ai/mastra/pull/30068; this branch includes
that fix from main.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

This PR lets users replace feedback without changing its identity. It
stores the replacement locally and sends it to supported exporters
without allowing delayed creates to overwrite it.

## Changes

- Added `PUT /api/observability/feedback/:feedbackId`.
- Preserved the feedback ID, trace ID, timestamp, and tenant.
- Cleared omitted optional fields.
- Added capability detection and `501` responses for unsupported
storage.
- Added replacement event types, SDK support, client types, route
metadata, and documentation.
- Added replacement delivery, stable retries, flush handling, and
shutdown draining for `MastraPlatformExporter`.
- Added replacement support for in-memory, PostgreSQL vNext, DuckDB, and
ClickHouse vNext.
- Added `onConflict: 'ignore'` for HTTP and exporter creates. Direct
storage calls retain their upsert default.
- Older exporters skip replacements instead of replaying them as
creates.
- Added ClickHouse support without a migration. Concurrent writes from
separate processes can still race.
- No UI changes were included.

## Validation

The author reports passing the HTTP route and contract suites, feedback
storage suites, partition and SQL tests, server and system tests,
record-builder tests, build, typecheck, lint, and documentation checks.

For the current head, the available CI result is `2027dev Evals:
skipped`. Other listed CI checks target different commits or remain in
progress. Current-head CI results are otherwise not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-11 17:04:57 +01:00
Eric Pinzur
166ad37deb
fix(observability): deliver feedback and scores independently to exporters (#30052)
Feedback and scores submitted with only a trace/span ID can be dropped
before reaching remote exporters because the SDK first looks in local
storage. For example, `addFeedback({ traceId, feedback })` cannot
currently reach Platform when that trace exists only there. This change
dispatches to every supporting exporter immediately and moves local
lookup/retries into MastraStorageExporter and the deprecated
DefaultExporter. Each storage exporter enriches its own copy while
preserving the original ID and timestamp.

OSS HTTP creates keep their existing local persistence and response
contract, then notify exporters without writing through the storage
exporter again. Supplied context, including an empty object, stays
supplied. Exported feedback preserves the author and review status,
including an explicitly null author. Pending storage lookups and custom
exporter deliveries are included in flush/shutdown. HTTP creates return
after local persistence and enqueue exporter delivery without waiting
for custom handlers to finish. Studio routing is unchanged: writes
target the backend serving reads.

Local context resolution requires the target span’s actual ancestor
root. Missing parents are retried, then logged and skipped locally; we
intentionally do not borrow another root’s tags or store incomplete root
context. Other exporters still receive the record independently.
Transient storage-read errors use the same bounded retry window and
report the final read error when exhausted.

Validated after review with 316 exporter/bus/recorded-span tests and 69
HTTP contract tests each on Hono, Fastify, and Koa (523 tests). The four
custom-exporter timing cases also passed 20 repeated runs. The
read-error and HTTP-latency regressions failed before their fixes, and
temporarily allowing the orphan fallback failed the new root-context
regression. Six older mocked forwarding/race tests are replaced by real
storage and HTTP coverage. Package builds, observability production and
adapter-suite typechecks, changed-file lint, and docs checks pass;
generated route types and CLI metadata are unchanged.

Express and NestJS tests hit a JSON body-parser failure before our
handlers. Standalone Express with no Mastra code reproduces `getBody is
not a function` under the local Node 23.11.0 runtime. The standalone
observability typecheck also retains four existing errors in
`workflow-control-flow-suite.ts`. These are not fixed here.

Fixes [OBS-886](https://linear.app/kepler-crm/issue/OBS-886) and
addresses the create-delivery portion of
[#24054](https://github.com/mastra-ai/mastra/issues/24054). Feedback
replacement remains in
[OBS-887](https://linear.app/kepler-crm/issue/OBS-887), and
review-status PATCH propagation remains in
[OBS-785](https://linear.app/kepler-crm/issue/OBS-785).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

This PR sends feedback and score records to each exporter independently.
Missing local traces no longer prevent remote delivery, and HTTP-created
records keep their original data.

## Summary

- Added exporter-specific event routing.
- Moved trace and span resolution into `MastraStorageExporter` and
`DefaultExporter`.
- Added bounded retries for storage lookups.
- Added pending annotation delivery before `flush()` and shutdown.
- Added asynchronous exporter notifications after successful HTTP
persistence.
- Prevented duplicate storage writes for HTTP-created records.
- Preserved IDs, timestamps, context, authors, anonymous feedback,
metadata, and review status.
- Added nullable `feedbackUserId` and `reviewStatus` support.
- Added SDK and HTTP adapter integration tests.
- Updated documentation, package metadata, and changesets.

**Diff:** 30 files changed; 954 additions and 483 deletions.

## Validation

- Reported: 503 focused tests passed, including 65 HTTP contract tests
for each of Hono, Fastify, and Koa.
- Reported: builds, changed-file lint, and documentation checks passed.
- Express and NestJS tests fail during JSON body parsing with `getBody
is not a function`.
- Standalone observability typecheck retains four existing errors.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-11 14:41:54 +01:00
Leo
8896651bd1
fix(server): stop custom route agent runs on client disconnect after GC (#29617)
## Description

### Summary

When a client disconnects from a custom API route that streams an agent
run (for example `chatRoute`), the run and its model request could keep
going. Server adapters re-dispatch custom routes through `new
Request(url, { signal })`. undici forwards the client abort to that
inner Request's own signal through a listener that holds the inner
controller only weakly (nodejs/undici#4068). Once the route returns its
streaming Response, nothing holds the inner Request, so a GC drops it
and the abort never reaches `c.req.raw.signal`.

The fix is in the shared `handleCustomRouteRequest` in `@mastra/server`,
so every custom route on every adapter gets it. The returned Response
gets a pass-through body whose closure holds the inner Request, and
drops it when the body is fully read, errors or is cancelled. Status,
status text and headers are unchanged; null-body responses are returned
as is.

```diff
 handleCustomRouteRequest(url, method, headers, body, requestContext, signal)
   const request = new Request(url, { ...init, signal })
   const response = await customRouteHandler(request, ...)
-  return response
+  return signal ? retainRequestWhileBodyIsOpen(response, request) : response
```

An earlier version of this PR used a `WeakMap<AbortSignal, Request>`
keyed by the client signal. Factory found it leaked every request whose
signal never aborts, which includes every normal Express response.
Cause: undici's `Request` constructor calls
`requestFinalizer.register(ac, { signal, abort })`, and a
FinalizationRegistry holds that held value (with the outer signal)
strongly while the inner controller lives, so signal -> WeakMap ->
request -> controller -> registry -> signal is a cycle the GC never
breaks. Holding the request from the body avoids the cycle: the body is
reachable exactly while an adapter is still sending the response.

```mermaid
flowchart LR
  A[client socket close] --> B[outer AbortController.abort]
  B --> C[undici listener on outer signal]
  C -. WeakRef .-> D[inner Request's controller]
  D --> E[c.req.raw.signal -> agent.stream abortSignal]
  G[adapter reading response body] ==> H[pass-through body]
  H == holds until done / error / cancel ==> F[inner Request]
  F --> D
```

### Evidence

Shared conformance suite `createCustomRouteDisconnectTestSuite`
(`@mastra/server-adapters-test-suite`), wired into Hono
(`@hono/node-server`), Express, Fastify, Koa and Elysia, over real HTTP:

1. Disconnect: a real `Agent` streams from a fake OpenAI-compatible
server, the route passes `c.req.raw.signal` as `abortSignal` (the same
wiring as `chatRoute`), the test forces GC, destroys the client socket,
and asserts the model request is aborted.
2. Release (new): a custom route streams a 201 response that completes,
or fails mid-stream; the test registers the inner `c.req.raw` and its
signal with a `FinalizationRegistry`, forces GC, and asserts both are
finalized.

| Server code | Disconnect | Release, completes | Release, fails
mid-stream |
|---|---|---|---|
| `origin/main` style, no retention | fails 5/5 adapters (`expected
'model request still running' to be 'model request aborted'`) | passes
5/5 | passes 5/5 |
| previous PR head 02fada0 (WeakMap) | passes 5/5 | fails 5/5 (`expected
[] to deeply equal [ 'request', 'request signal' ]`) | fails on Elysia;
others abort the signal on a broken body |
| this head | passes 5/5 | passes 5/5 | passes 5/5 |

- **Stability:** with the fix, 40/40 adapter suite runs passed (5 runs
of the 2-test suite plus 3 runs of the 3-test suite, on each adapter).
An independent reviewer ran Express and Hono 20 times each, all passing.
- **Factory's measurement, reproduced** (`new Request(url, { signal })`,
80 forced GCs, `FinalizationRegistry`):

| Node (undici) | No map | `WeakMap.set(signal, request)` | WeakMap +
abort |
  |---|---|---|---|
| v24.22.1 (7.30.1) | both finalized | neither finalized | both
finalized |
  | v22.22.1 | both finalized | neither finalized | both finalized |

- **Issue repro script** (`chatRoute` + `createNodeServer`, `node
--expose-gc`): `aborted after disconnect: false` before, `true` after,
on Node 24.22.1 and 22.22.1. CI runs Node 24.22.1, where the bug
reproduces.
- **No regressions:** `@mastra/server` `src/server/server-adapter` unit
tests 434/434. `tsc --noEmit` for `@mastra/server` and the test suite,
`oxfmt --check` and `oxlint --deny-warnings` are clean on the changed
files. The reviewer also checked status, status text, multiple
`set-cookie`, mutable headers (Fastify merges plugin headers into the
returned Response), explicit `content-length`, and Hono's node-server
`Response` override.
- **Not covered:** native Bun (Elysia's test runs on a Node HTTP shim;
Bun's `Request` isn't undici). `@mastra/nestjs` custom routes don't
forward a client abort signal at all, which is a separate gap this PR
doesn't touch.

### Merge Danger

**Door:** two-way. One helper in `server-adapter/index.ts` plus tests
and changesets; a revert undoes it.

**Blast radius:** every custom API route response with a body, on every
adapter. The body now passes through one extra `ReadableStream`: one
extra async read per chunk, and no BYOB reads of the route's body. On
Hono, `@hono/node-server` can no longer infer `content-length` for a
small non-streamed custom route body (for example `c.json(...)`), so it
goes out chunked unless the handler sets `content-length` itself.
Express, Fastify and Koa already pipe custom route bodies as chunked. A
body an adapter keeps but never reads or cancels keeps its request until
the body is collected; no adapter does that today. Conflicts: none with
#29549 (`feat(ai-sdk): add reconnectable chat routes`), which rewrites
`client-sdks/ai-sdk/src/chat-route.ts`; this PR does not touch that
file.

## Related issue(s)

Closes #29154

## Type of change

- [x] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [x] Test update

## Checklist

- [x] I have linked the related issue(s) in the description above
- [ ] 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

## Council review

Rounds: 3

| Seat | Round 1 | Round 2 | Round 3 (request release follow-up) |
| --- | --- | --- | --- |
| Claude Opus 5.5 | not run | 9/10 (Correctness 9, Tests 9, Scope 10,
Code quality 9) | not run |
| GPT-6.1 Sol | 9/10 (Correctness 9, Tests 9, Scope 10, Code quality 9)
| 9/10 (Correctness 9, Tests 9, Scope 10, Code quality 9) | 9/10
(Correctness 9, Tests 9, Scope 10, Code quality 9), no findings |
| Grok 4.7 | empty seat | empty seat | empty seat |

Created with Claude Opus 5.5 in T3 Code.

🤖 Generated with [Claude Code](https://claude.com/claude-code)


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

When a client disconnects during a streamed response, the server keeps
the request alive until the response ends, fails, or is cancelled. This
allows the disconnect to stop the agent and model request after garbage
collection.

## Changes

- Updated `handleCustomRouteRequest` to retain the re-dispatched
`Request` while a response body is active.
- Preserved response status, status text, and headers.
- Left null-body responses unchanged.
- Added shared tests for disconnect handling and request release.
- Added test setups for Hono, Express, Fastify, Koa, and Elysia.
- Exported the shared test suite and configuration type.
- Added patch changesets for `@mastra/server` and
`@mastra/server-adapters-test-suite`.

**Diff size:** 10 files; 504 lines added and 1 removed.  
**CI, build, and test results:** not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 03:34:38 -05:00
dane-ai-mastra[bot]
8bce7717eb
chore: version packages (alpha) (#29986)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-11-10 20:51:40 -08:00
dane-ai-mastra[bot]
23cc34a9c5
chore: version packages (alpha) (#29938)
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>
2026-11-10 15:51:29 -08:00
Daniel Lew
2dbb9c83b3
test(server): harden the Observational Memory ownership tests and correct the changeset (#29955)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-10 16:12:20 -05:00
Daniel Lew
94bf8761f4
fix(server): enforce thread ownership on gateway Observational Memory routes (#29926)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-10 12:36:51 -08:00
Arthur Fiorette
d50e8b275d
fix(elysia): accept empty JSON bodies and end failed streams cleanly (#29944) 2026-11-10 12:22:09 -08:00
dane-ai-mastra[bot]
779d2875b1
chore: version packages (alpha) (#29912)
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>
2026-11-10 10:50:08 -08:00
shreyas-mastra
ce76df95d5
fix(server): check auth against the custom route that handles the request (#29325) 2026-11-10 09:21:04 -08:00
shreyas-mastra
134d4f14c2
fix(nestjs): enforce per-route body size limits on JSON requests (#29476)
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 -->
2026-11-10 10:46:46 -05:00
dane-ai-mastra[bot]
7c4dd88400
chore: version packages (alpha) (#29889)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-11-10 15:48:17 +01:00
Ward Peeters
b2ce66cef8
chore: run lint-staged for root files and the 16 packages without a config (#29898)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-10 14:08:55 +01:00
Ward Peeters
536b8bd4be
test: fix three tests that keep failing release and adapter CI runs (#29900)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-10 13:22:18 +01:00
dane-ai-mastra[bot]
6deb16047f
chore: version packages (alpha) (#29719)
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>
2026-11-10 10:33:29 +01:00
mastra-platform[bot]
4854e36419
fix(core, server): stop a peer server from approving an aborted parked durable run (#29799)
> Opened by @user_01KNA8J74D4RF84RXSDRX26BS9

## Problem
A durable agent run that is waiting for tool approval (with no thread)
can be aborted over HTTP. The abort returns `200 {"aborted":true}`, but
that was only recorded in memory on the server that handled the abort.
When the app runs on more than one server, approving the tool call on a
different server still resumed the run and **ran the tool**. When the
abort and approval happened on the same server, the approval was
rejected with a `500` rather than a clear error code. Fixes COR-1518.

## Fix
- **Abort saves the cancellation in storage before it is acknowledged**
(`packages/core/src/agent/durable/durable-agent.ts`):
- Stores that support concurrent updates: a guarded
`updateWorkflowState({ status: 'canceled', expectedStatus: 'suspended'
})`.
- Stores without `updateWorkflowState` (snapshot-only, e.g. LanceDB) and
stores without concurrent updates (e.g. Redis): reread the run, then
rewrite its snapshot as `canceled` with `persistWorkflowSnapshot(...,
expectedStatus: 'suspended')`, keeping `resourceId`.
- Storage errors propagate. The abort does not report success while the
run can still be resumed.
- If a resume has already claimed the run (status `running`), the
guarded write makes no change, and the existing abort of a running run
applies.
- **Resume on any server rejects runs canceled in storage** with
`AGENT_RESUME_ABORTED_RUN`, before it claims the run. The in-flight
resume marker is still taken synchronously before the first `await`
(#27365); the storage check runs right after it and releases the marker
when it rejects the run.
- **Observers of a canceled run are closed on every server**: the abort
that wins the `suspended → canceled` write publishes the abort event
right away on the shared pubsub, so `observe` streams on all servers end
and their history/listeners are cleaned up; the `canceled` row is kept.
If that publish fails, the abort still succeeds (the cancel is stored)
and a later refused approval/resume on that server retries the publish.
- **Docs and changeset**: `docs/.../agents/resumable-streams.mdx` and
`reference/agents/durable-agent.mdx` now point parked runs in
multi-server apps at `POST /agents/:agentId/runs/:runId/abort`, describe
the stored cancellation and the `409 Conflict`
(`AGENT_RESUME_ABORTED_RUN`) refusal, and qualify `abortRunStream` as
process-local. The changeset is scoped to
`DurableAgent`/`createDurableAgent` (evented agents inherit it; Inngest
agents are not covered) and states the best-effort limit on stores
without concurrent updates.
- **Approve route** (`packages/server/src/server/handlers/agents.ts`): a
`canceled` snapshot is treated as final instead of waiting 10s for a
suspension. The resource, thread and agent ownership checks still run
first, so other callers get `403` and learn nothing about the abort.
- **API contract** (`packages/server/src/server/handlers/error.ts`):
`AGENT_RESUME_ABORTED_RUN` now maps to **`409 Conflict`**, joining the
existing resume-claim conflict codes. It used to fall through to a
`500`.

## Proof
**Lifecycle regressions found in review and fixed in this PR** (final
head `1e0af6b5e8`):
1. *Healthy-lifecycle regression* (found by independent review at
`635c8837e3`): after a same-server abort and refused approval, an
attached observer stayed open and the run's history/listeners were
retained, because the `canceled` row skipped the old abort event. Fixed
in `c4cbdb987a`.
2. *Failed-first-publish recovery* (found by independent review at
`c4cbdb987a`): if publishing that abort event failed once, later
refusals never retried it and the observer stayed open. Fixed in
`7a856a33a3`, which also restores the #27365 marker ordering.
3. *Cross-server observer gap* (found by review at `7a856a33a3`): when
the abort and the refused approval landed on different servers,
observers stayed open because only the refusing server's local fence
published the abort event. Fixed in `6d444bee4f` by publishing at abort
time from the cancel winner.
4. *Human review (NikAiyer)*: docs, changeset scope, and a test that
pins the guarded write — addressed in `1e0af6b5e8`.

**Author: in-repo tests at final head `1e0af6b5e8`**
-
`server-adapters/hono/src/__tests__/parked-run-abort-across-servers.test.ts`:
two Hono servers over real TCP. They share a store and cache, and each
has its own pubsub and runtime state. 10/10 pass:
  - No abort, approve on the other server: `200`, tool runs once.
- Abort on the executing server, approve on the other server: `409`,
tool runs 0. **On main this returns 200 and the tool runs once (the
bug).**
- Abort on the other server, approve there: `409`, tool runs 0. Abort
and approve on the executing server: `409`, tool runs 0. On main both
return `500`.
- In all three abort rows, observers attached on **both** servers close
within 2s with exactly one abort frame each. With core from `7a856a33a3`
the executor-abort/other-approve row fails (observers stay open);
removing the abort-time publish makes it fail again.
- Another user's approval of an aborted run gets `403`, and so does
approval through another agent. In both cases the abort is not revealed.
- Race: a run that a resume has already claimed stays `running` after
the abort.
- Race inside the abort: a resume claims the run between the abort's
status read and its guarded write → the abort returns `200
{aborted:false}` and the run stays `running`. Removing `expectedStatus:
'suspended'` from the write makes this test fail.
- Observer: observe → abort → two refused approvals (409, 409) → the
observer closes within 2s, exactly one abort event is published, the row
stays `canceled`, and a peer approval still gets 409 with tool runs 0.
At `635c8837e3` the observer stays open; removing the once-guard
publishes 2.
- Failed first publish: the abort's own publish rejects, then the broker
recovers → the next refused approval on that server republishes → the
observer closes, one abort published, tool runs 0. Removing the
reservation release makes it fail (observer open, 0 published).
- `stores/lance/src/storage/parked-run-abort.test.ts`: real LanceDB with
two peers. After the abort, status is `canceled` and the peer's approval
is rejected with `AGENT_RESUME_ABORTED_RUN`, tool runs 0. Running it
with only the first commit fails with `updateWorkflowState is not
implemented`.
- `packages/server/src/server/handlers/error.test.ts`: 27/27 pass,
including the new 409 mapping.
- Revert checks: undoing the core change brings back `200`/1 tool run;
undoing the error mapping gives `500`; undoing the approve-route change
makes the approval wait out the 10s timeout.

**Author: real Redis, two processes — run on earlier heads
(`635c8837e3`/`c4cbdb987a`/`6d444bee4f`), NOT on the final head
`1e0af6b5e8`; this harness does not check observer closing** (two Node
processes running Hono, each sharing `RedisStore`, `RedisServerCache`
and `RedisStreamsPubSub` on a local Redis 7, using the public HTTP API)
| scenario | abort | approve on peer | tool commits |
|---|---|---|---|
| no abort | n/a | 200 | 1 |
| abort on executing server | 200 `{aborted:true}` | 409
`AGENT_RESUME_ABORTED_RUN` | 0 (main: 200, 1) |
| abort on peer | 200 | 409 `AGENT_RESUME_ABORTED_RUN` | 0 (main: 500,
0) |

**Independent reviewer** (separate session): approved the exact final
head `1e0af6b5e8`, including the `6d444bee4f` runtime change. Hono
10/10, HTTP ownership 4/4, Lance 1/1, resume-claim tests 37, build and
tsc. Failed-first-publish recovery and observer cleanup on both peers
were proven with real-TCP probes. Earlier rounds approved `635c8837e3`
(Lance 1/1, Hono 7/7; a LanceDB abort that returned `500` on the first
commit now returns `200` and the canceled snapshot keeps its other
fields) and `7a856a33a3` (concurrent refusals publish one terminal;
resume-marker release).

**Measured caveat (independent reviewer):** with simultaneous aborts,
the single CAS winner publishes one terminal and that closes the
observers on both servers; each original observer sees exactly one
abort, every approval gets `409`, and the tool runs 0 times. But a
**later** approval on the server whose abort lost the race can publish a
**second** terminal, because the once-guard is a per-instance set; after
cleanup this leaves 1 history entry retained. This PR does **not**
guarantee a globally-once terminal or unconditionally empty history.

Checks: tsc passes for core, server and hono. Lance oxlint is clean.
Prettier is clean on the changed lines; `agents.ts` already fails
Prettier on `main`, and that existing drift is left alone.

## Self-review (board self-review, approved at `635c8837e3`; the later
lifecycle fixes were approved by the independent re-review above)
The run abort route now records the cancellation in shared storage, and
every later resume or approval checks it on any server before anything
runs. A blocked approval returns `409 AGENT_RESUME_ABORTED_RUN`.
Adversarial check: if the resume claims first, the abort's guarded write
fails and the run stays `running` (tested). If the abort writes first,
the resume either sees `canceled` and gets 409, or loses its own claim
and gets the existing claim-lost 409. Authorization runs before the
canceled state is revealed. Nothing blocking was found.

| Check | Result | Tests |
|---|---|---|
| Build `@mastra/hono...` + `@mastra/lance...` | ✅ | — |
| Hono two-server HTTP (`parked-run-abort-across-servers.test.ts`) | ✅ |
7/7 |
| LanceDB parked abort (`parked-run-abort.test.ts`) | ✅ | 1/1, plus 8
reruns including under CPU load (1 early failure that could not be
reproduced) |
| Server error mapping (`error.test.ts`) | ✅ | 27/27 |
| Core durable suite (both storage projects, type-check on) | ❌ | 3966
passed, 1 failed, 4 skipped; no type errors |
| That failing file rerun on its own
(`durable-agent-tool-call-resumed.test.ts`) | ✅ | 30/30 |

Not run by self-review: a revert of the production files to re-run the
Hono test against the old code (Linear's main repro stands in for it,
and the author's revert checks above cover it); a real two-process Redis
run (covered by the author's harness above); repo-wide lint/format.

## Unverified
- The full Hono adapter suite was not run to completion.
- In the core durable suite, `durable-agent-tool-call-resumed.test.ts >
applies the display transform…` failed once with
`AGENT_RESUME_ALREADY_CLAIMED` and passed when run on its own. It looks
like test-isolation contention, not a confirmed cause. Separately,
`durable-agent-crash-recovery.test.ts` runs out of memory on `main` too.
- The Redis two-process harness was not run on the final head, and it
does not check observer closing; the cross-server observer tests use an
in-process shared-emitter pubsub, not Redis.
- A truly concurrent abort and approval on stores without concurrent
updates was not tested.

## Risk
- On stores without concurrent updates (Redis, Valkey, Elasticsearch,
LanceDB, ClickHouse, Cloudflare KV/DO), the canceled write is
**best-effort, not atomic**: the status is checked and then the snapshot
rewritten. An approval that lands between the two can still go ahead.
This PR does **not** guarantee that a racing abort and approval resolve
cleanly on every store; it guarantees that an abort that has already
completed is honored on every server. No new `supportsConcurrentUpdates`
requirement is added.
- The abort-event dedupe is per process and bounded (1000 run ids). It
is not global: see the measured caveat above (a later approval on the
losing-abort peer can publish a second terminal and retain one history
entry).
- A failed abort-time publish is retried only by a later refused request
on the aborting server; a peer's refusal does not retry it, and there is
no background retry.
- Aborted parked runs now keep a `canceled` row instead of a `suspended`
one.
- The thread abort route (`__abortThreadStreamAcrossProcesses`) does not
write the storage fence. That is out of COR-1518's scope.
- An abort that arrives while the run is still executing and parks just
afterwards keeps the existing behavior.
- `AGENT_RESUME_ABORTED_RUN` is also thrown by the non-durable `Agent`,
which now also gets `409` instead of `500`.



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

When a run pauses for tool approval, canceling it now records that
decision so another server cannot approve the run and start the tool.
This helps prevent canceled work from continuing elsewhere.

## Summary

- Persist cancellation for parked `DurableAgent` runs before confirming
the abort. Use a guarded status update when the storage adapter supports
concurrent updates. Otherwise, save the updated snapshot. On adapters
without concurrent updates, an approval that overlaps the save may still
proceed.
- Reject approval or resume attempts for canceled runs with
`AGENT_RESUME_ABORTED_RUN`. Check ownership before returning `409
Conflict`.
- Publish an abort event after cancellation so observers can close. If
publication fails, a later refused resume can retry it.
- Add cross-server integration tests and a LanceDB regression test.
Update the documentation to describe the behavior and clarify that it
applies to `DurableAgent`, not Inngest agents.

## Validation

Reported final-head results: the Hono two-server test passed 10/10, the
LanceDB test passed 1/1, and the server error-mapping test passed 27/27.
Core, server, and Hono type checks passed. The core durable suite
reported 3,966 passed and 1 failed; the failed test passed when rerun
alone. The full Hono suite was not completed. The Redis two-process
harness ran on earlier heads, not the final head. Repository-wide lint
and format results are not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-09 20:49:41 -08:00
mastra-platform[bot]
8a10dfe648
fix(core): allow authorized finished durable replay across servers (#29791)
## Summary

Fix finished `DurableAgent` and evented-agent output replay returning
404 on a different server while the executing server can still replay
the same retained output.

- Publish shared, read-only replay ownership before execution starts;
remove it alongside replay-history cleanup.
- Consult that ownership only for observation when persisted workflow
ownership is missing. Explicit denials and unverifiable workflow rows
remain authoritative, and existing resource, RequestContext, thread and
FGA checks still apply.
- Keep abort/write authorization separate: replay ownership never
permits stopping a finished run.
- Add real-TCP Hono regressions for durable/evented replay, ownership
denial, thread-read denial, anonymous access, finished abort, unknown
runs and post-cleanup 404; include core/server patch changesets.

Fixes COR-1512. Independent branch from main; no COR-1518 cancellation
or COR-1517 snapshot changes.

## Proof

Reviewed candidate: `c412839fb8`, based on
`6bc7614a8f`.

Author verification:
- Real local Redis, two HTTP processes: baseline owner replay was 200 on
executor / 404 on peer for durable and evented agents; candidate returns
200 / 200. Foreign users receive 403 / 403, anonymous callers 401 / 401,
and both servers return 404 after cleanup. Finished abort remains `{
aborted: false }`. The Redis ownership key is present during the replay
window and removed after cleanup.
- Reverting the production changes makes both committed durable/evented
regressions fail with peer 404.
- Core/server/Hono typechecks, changed-file lint/format, 290 server
agent tests, full Hono suite and 62 affected durable test files passed.

Independent exact-head review:
- Fresh core/server builds and core build typecheck passed; verified
candidate module resolution rather than stale distributions.
- 381 committed tests passed: 8 TCP replay/access tests, 315 server
ownership/agent tests and 58 focused core lifecycle/cleanup tests.
- Additional handler-level probes verified RequestContext-dependent
memory, denied/unverified workflow rows never consulting shared
ownership, cache-read failure returning 503, WRITE never using replay
ownership, and owner-publication failure preserving live completion
while remote access fails closed.

## Unverified

- The committed TCP tests share in-memory objects within one process.
The author's two-process Redis harness is uncommitted and was not
independently rerun; Redis results above are author evidence, not
independent proof.
- No hosted Redis, cluster/TLS/failover, load, browser, full-repository
CI or real Inngest replay qualification. The separate Inngest proxy does
not acquire the new replay-owner capability in this patch.
- Fresh GitHub CI and maintainer review remain pending.

## Risk

Adds one bounded shared ownership record per durable run. Its TTL is 24
hours; normal deletion follows existing replay cleanup and ownership
guards. Cleanup remains best effort/asynchronous, not a transaction
promising retention under backend failure. Cache expiry/eviction can
shorten access, and failed owner publication can leave peer replay
unavailable while the initiating response succeeds. Existing
unique-run-ID requirements remain unchanged; this is not a new
namespace, reuse protocol, durable event log or write/cancellation
authority.

Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-09 12:32:03 -08:00
Arthur Fiorette
efa3999a21
fix(server-adapters): stop reading route streams after the client disconnects (#29669)
## 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 #29640
Fixes #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 -->
2026-11-09 09:59:22 -08:00
dane-ai-mastra[bot]
009f632534 chore: version packages 2026-11-09 04:19:07 +00:00
mastra-platform[bot]
5b03e9ce69
refactor(server): share authorization for observing and aborting agent runs (#29600)
## Summary

Route agent-run observation and cancellation through one shared
authorization policy so ownership and thread-permission checks do not
drift between the two endpoints.

- Observe continues to require `MEMORY_READ`; abort continues to require
`MEMORY_WRITE`.
- Preserve resource ownership, RequestContext/Studio FGA selection,
thread access checks, and fail-closed handling of missing or
unverifiable ownership.
- Preserve existing route responses and cancellation acknowledgement:
authorization alone never means a run was stopped.
- Add real HTTP regressions for plain and durable agents, including
access during the first model call, and a server PATCH changeset.

This is the independent server authorization lane of the stream-layer
work. It is based directly on `main`, does not contain the core/Inngest
session-extraction branch, and imports no new core APIs. No peer-floor
changes are needed. Production changes are limited to
`packages/server/src/server/handlers/agents.ts`.

## Behavior deliberately preserved

Plain runs resolve ownership through shared run records and the existing
published-owner compatibility fallback. Durable observation can use the
local run owner before falling back to persisted workflow ownership.
Durable cancellation still requires verifiable workflow ownership; the
retained observation registry is not evidence that a finished run
remains cancellable.

Unknown observation returns 404. Unknown plain cancellation returns 404;
unknown/unverifiable durable cancellation returns `{ aborted: false }`.
Finished plain runs return `{ aborted: false }`. Existing 403/501/503
handling, recovery, and acknowledged-abort dispatch remain unchanged.

## Proof

Implementation candidate: `8b5c87e319`.
Release-metadata candidate `f46b980ef7`
adds only the server PATCH changeset; the test-only follow-up below is
the current head.

- Author verification: **281/281** server agent-handler tests and
**98/98** Hono run-access, durable-disconnect, and recovery-checkpoint
tests passed. Server TypeScript and changed-file lint passed.
- New real-TCP access cases cover owner/read-only viewer/foreign
tenant/anonymous requests, unknown runs, wrong-agent targeting,
confirmed tool cancellation, and first-model-call cancellation for plain
and durable agents. They also pass on unchanged baseline, as expected
for a behavior-preserving refactor.
- Mutation proof: authorizing cancellation with READ instead of WRITE
fails four cases; removing durable ownership validation fails two cases.
- Independent review found no actionable defect. It reran **281/281**
handler tests and **4/4** new TCP cases, rebuilt the candidate server,
verified the new helper in the generated runtime, and reran **4/4** TCP
cases against that fresh runtime. These repeat checks are not additional
unique test counts.
- Prior verified base `f46b980ef7`: **8/8
real Redis two-process tests passed**, no skips. Two HTTP server
processes shared Redis Streams/cache and LibSQL, with AIMock only at the
model HTTP boundary. Coverage includes cross-server owner
replay/approval/finish, confirmed abort with replay enabled/disabled,
tenant/anonymous/unknown-run denial, parked abort nonconfirmation, and
ownership expiry/cleanup. Candidate core/server builds succeeded;
runtime source maps matched candidate sources.
- Parent review verified independent ancestry and disjoint production
files from the core/Inngest extraction. The changeset-only follow-up
passed package-target/frontmatter validation and `git diff --check`; it
changes no runtime or tests.

## Test-only read-denial follow-up

Current head: `71d868c384`, a +7-line
change confined to
`server-adapters/hono/src/__tests__/run-access-http.test.ts`. Production
sources and existing read grants/write restrictions are unchanged.

- Add a same-resource caller denied `memory:read` and require HTTP
observe **403** for both plain and durable agents.
- Candidate core/server rebuilt; **4/4 real-TCP tests passed**. After
restoring and rebuilding the server following mutation, **4/4 passed**
again.
- Causal mutation: bypass only `MEMORY_READ` thread enforcement while
retaining resource-ownership and write controls. Both new plain/durable
assertions fail with **200 instead of 403**; the two first-model-call
write-control cases still pass. The mutation was removed before
committing.
- Formatting, type-aware lint, Hono `tsc --noEmit` (package config
excludes tests), and `git diff --check` passed.
- The earlier **8/8 Redis two-process proof remains evidence for base
`f46b980ef7` only**; it was not rerun for
this test-only follow-up. Fresh CI for
`71d868c384` is pending.

## Unverified

- Full monorepo CI and eventual combined execution with the
still-in-progress core/Inngest session extraction.
- Hosted Redis, cluster/TLS/failover, production load, real
Inngest/evented authorization, and browser flows were not independently
exercised in this lane.
- Malformed persisted snapshots and existing compatibility fallbacks
were not redesigned.

## Risk

This changes security-sensitive control flow even though route behavior
is intended to remain identical. The shared helper retains the
established READ/WRITE distinction and existing ownership-store
fallbacks rather than introducing new authorization or liveness rules.
Abort confirmation remains a separate operation after authorization.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

The observe and abort routes now use the same rules to check who owns a
run and who can access its thread. Watching needs read permission, while
stopping needs write permission.

## Changes

- Added `authorizeRunAccess` in
`packages/server/src/server/handlers/agents.ts` and used it for both
routes.
- Kept route-specific responses for unknown, finished, and unverifiable
runs.
- Added an agent-handler regression test. It confirms an in-process
owner record alone does not authorize aborting a durable run.
- Added HTTP-over-TCP tests for plain and durable agents. They cover
access permissions, unknown runs, and aborting during a tool call or the
first model call.
- Added a patch changeset for `@mastra/server`.

**Diff:** 4 files changed; 275 lines added and 34 removed.  
**Test results:** The author reports 4/4 real-TCP tests passed. Fresh CI
for the current head is pending.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-08 09:57:03 -08:00
dane-ai-mastra[bot]
f21e0742ce chore: version packages 2026-11-07 04:18:11 +00:00
mastra-platform[bot]
c18f4211c8
fix(express): cancel the response stream when the client disconnects (#29636)
## Summary

The Express adapter now cancels the response stream reader when the
client disconnects, the same way the Hono and Fastify adapters do.
Before this, Express kept reading every dropped stream to the end, and
durable or evented agents on `untilIdle` routes returned 404 "Run not
found" from `/observe` right after a client drop.

## Root cause

`ExpressServerAdapter.stream()` (`server-adapters/express/src/index.ts`)
never listened for the response `close` event, so the reader was never
canceled on disconnect. The `untilIdle` wrapper therefore never set
`observerDetached`; its idle timer called `forceClose()` without
`keepInnerRuns`, durable cleanup ran as soon as the run finished, and
the run was gone before `/observe` could replay it.

Hono cancels on `stream.onAbort`, Fastify on the raw `close` events.
Express now registers `res.on('close')`, cancels once (ignoring the
cancel rejection, as both other adapters do), and removes the listener
when streaming ends.

The shared durable-disconnect suite had a
`skipUntilIdleDisconnectReplay` option that only Express used to skip
these 8 cases. It's removed, so the cases run on every adapter. Most of
the suite diff is Prettier reindenting the test body after
`it.skipIf(...)` became `it(...)`.

## Test plan

- Express durable-disconnect suite with the fix: 98/98 pass, none
skipped.
- Same suite with only `src/index.ts` reverted: 8 fail (`stream-alias`,
`stream-until-idle`, `resume-alias`, `resume-stream-until-idle`, for
both durable and evented) with `expected '{"error":"Run not found"}' to
contain 'done: 3 results'`.
- Hono and Fastify durable-disconnect suites: 98/98 each.
- Full Express test run passes.
- `tsc --noEmit`, `oxlint`, and `prettier --check` are clean on the
touched packages.

Fixes #29634


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5
When a client disconnects, Express now stops reading the response stream
that the client cannot receive. This can keep eligible runs available
for replay and lets the shared disconnect-and-replay tests run for
Express.

## Changes
- Express cancels each stream reader at most once when the response
closes. It ignores cancellation errors and removes the close listener
when streaming ends.
- If the response is already destroyed when Express adds the close
listener, Express cancels the reader immediately.
- Added tests for disconnects during `datastream-response` and `stream`,
including disconnects before the route handler returns.
- Removed `skipUntilIdleDisconnectReplay` from the shared
durable-disconnect test configuration and suite.
- Added patch changesets for `@mastra/express` and
`@mastra/server-adapters-test-suite`.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: NikAiyer <nick.aiyer@gmail.com>
2026-11-06 19:58:17 -08:00
mastra-platform[bot]
d6a5f98df3
fix: index observe chunks for resume (COR-1506) (#29520)
> Opened by @user_01KNA8J74D4RF84RXSDRX26BS9

Linear:
[COR-1506](https://linear.app/kepler-crm/issue/COR-1506/observe-offset-cant-be-used-to-resume-it-counts-log-events-but-clients)

## Problem

`observe({ runId, offset })` takes `offset` as a position in the run
log. Clients can't compute that position:
- Some log entries never reach the client. These include
iteration-complete records after every step and ownership markers.
- Updates on the wire carried no index.

A client that resumes at "number of updates received" lands too early
and gets repeated updates. The drift grows by one per completed step, so
every tool-using run that reconnects after its first step is affected.
On a 3-step tool loop, 16 of 28 cut points repeated 1–2 updates on both
durable and evented engines.

## Fix

- **Index on updates:** every update now carries `index`, the run-log
position it came from. This covers:
  - `/observe` on every agent
  - `/stream` on durable and evented agents
- core `stream()`/`observe()` chunks and client-js
`observe()`/`stream()`
- **Resuming:** pass `index + 1` of the last received update that has an
index as `offset`. Gaps in the numbering are expected; they're log
entries that send nothing.
- **Unindexed updates:** the synthesized `abort` update carries no
index. Its log position is on the `finish` sent beside it. Client-built
structured-output `object` chunks have no index either. An
`object-result` logged by a structuring-model run carries one. Unindexed
updates don't move the resume point. A client that reconnects between
`abort` and `finish` gets the `abort` again.
- **`offset` is unchanged:** it still means a run-log position.
- Core no longer strips `index` in
`DurableAgent.__subscribeToRunStream`. The stream adapter and the
server's `toAgentStreamChunks` copy the envelope's index onto each chunk
and drop any index a forwarded sub-agent chunk carried. `index` is
optional on `BaseChunkType` and `DataChunkType`.
- **Also fixed:** on plain agents, `/observe` (HTTP and core
`agent.observe()`) with an offset past the end of a finished run used to
wait for the idle timeout or hang. It now closes immediately. It reads
the log from just before the offset and only falls back to a full read
when that window is empty. The check runs in the background, so it never
delays returning the stream or its cancel handle. A trailing `error`
chunk doesn't count as the end of the run.

## Migration

`index` is a new field and `offset` keeps its meaning:
- Callers that pass a log position need no change.
- Callers that replay from `offset: 0` need no change. They get the same
updates in the same order, now with `index` set.
- Only callers that passed a count of updates received need to change.
They were already getting repeats after step boundaries; switch them to
`index + 1` of the last indexed update.

## Evidence

| Check | Result |
| --- | --- |
| Red/green | With `main`'s core and server, 15 tests on numbering and
`/stream`–`/observe` matching fail; with this change all pass. |
| Cut points | Every cut point of a 3-step tool loop on durable and
evented engines resumes from the first `/stream` connection at last
index + 1. Covers the HTTP route and client-js `stream()` → `observe()`.
|
| `/stream` vs `/observe` match | Frames are identical JSON, including
`index`. Replay from 0 equals the first `/stream`. |
| End of run | Resume after finish or past the end returns the rest and
closes, including far past the end (offset 100). |
| Adapters | Hono 98/98, Fastify 98/98, Express 90 passed + 8 skipped
(see bug 1 below). The shared suite is now wired into Express and
Fastify. |
| Redis restart | Real-Redis split-deploy test (in
`pubsub/redis-streams/src/observe-cross-process.test.ts`) passes on both
engines. The client resumes on a freshly booted API process at last
index + 1 with nothing repeated or missing. Evented: the worker executes
the run and the API is killed with SIGKILL. Durable runs execute in the
API that started them, so that API stays up; the client drops its
connection and resumes on a second API. |
| Suspend | After tool approval, indexes keep increasing. Observers
parked mid-suspend and every cut across the suspend resume correctly on
both engines. |
| Unit suites | server `agents.test.ts` 289, core `src/stream` +
`src/agent/streams` 481 |
| Static | tsc clean on core, server, client-js, the test suite, the
Hono/Express/Fastify adapters and redis-streams. oxlint 0 warnings. |

## Scope

Plain (non-durable) agents' `/stream` updates aren't numbered yet. The
caller receives each update before the cache assigns its number. That's
tracked in COR-1510. Plain agents' `/observe` is covered here.

## Existing bugs found (not fixed here)

1. **Express untilIdle 404:** after a client drops an untilIdle stream
on a durable or evented agent, Express answers `/observe` with 404 "Run
not found". It fails the same way on `main`. Those 8 cases are skipped
on Express only, via `skipUntilIdleDisconnectReplay`.
2. **Finished durable run, other API:** a finished durable run returns
404 on `/observe` from any API process except the one that executed it
(`authorizeDurableRun`, `handlers/agents.ts`). Resuming while the run is
live works from any API.
3. **Plain replay mismatch:** on plain agents, replayed
`step-finish`/`finish` payloads differ from the live ones (for example
`timestamp` and `processorRetryCount`). Related to COR-1510.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

When a connection drops, clients need to know which updates they already
received. This change adds positions to many updates so clients can
resume from the right place. It also closes observations of finished
runs when the requested position is past the end.

## Summary

- Added optional `index` values to chunks from durable and evented agent
streams, `observe()` streams, and corresponding HTTP routes. Clients can
resume by passing the last indexed chunk’s `index + 1`.
- Preserved run-log indexes through core stream adapters and server
frame conversion. Sub-agent data chunks do not carry a child run’s index
into the parent stream.
- Some chunks remain unindexed, including synthesized `abort` chunks and
client-built structured-output `object` chunks. Failed cache writes and
non-atomic custom-cache indexing can affect replay.
- Updated API schemas and documentation to explain index gaps, replay
limits, and resumption.
- Added past-end handling for finished plain-agent observations in core
and HTTP `/observe`. History checks do not delay stream return or
prevent cancellation.
- Added tests for indexed replay, past-end closure, cancellation during
history reads, sub-agent index isolation, and observation across API
restarts.

**Validation:** Current-head CI, build, and test results are not
available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: NikAiyer <nick.aiyer@gmail.com>
2026-11-06 11:40:46 -08:00
Eric Pinzur
23308f9c19
feat(observability): add single score and feedback reads (#29529)
## Description

Add `GET /observability/feedback/:feedbackId` and typed client getters
for individual scores and feedback. Missing records return HTTP 200 with
`{ score: null }` or `{ feedback: null }`, preserving the existing score
endpoint contract.

```ts
const { score } = await client.getScore(scoreId);
const { feedback } = await client.getFeedback(feedbackId);
```

Client getters encode path IDs and preserve configured API prefixes,
credentials, and headers. Feedback reads use direct lookups in
in-memory, PostgreSQL, ClickHouse, and DuckDB storage. Includes
generated route types/CLI metadata, public API documentation, and
changesets.

Validation: package builds passed; 30 single-record HTTP cases passed
across five server adapters; 6 client transport tests, 341 server tests,
and 9 focused database cases passed across PostgreSQL/TimescaleDB,
ClickHouse, and DuckDB. Removing the feedback route caused the new
feedback HTTP cases to fail. Permission generation/checks, scoped
implementation lint, MDX formatting, Remark, and Vale passed.

Broader validation limitations: existing POST cases fail with
body-parser dependency errors in Express, Koa, and NestJS; the new GET
cases pass in all five adapters. The shared storage test helper also has
existing import-order lint errors outside the changed lines.

## Related issue(s)

Fixes
[OBS-790](https://linear.app/kepler-crm/issue/OBS-790/add-oss-single-score-and-feedback-reads),
under [OBS-792](https://linear.app/kepler-crm/issue/OBS-792). Platform
single-record endpoints remain scoped to OBS-791.

## Type of change

- [x] New feature (non-breaking change that adds functionality)
- [x] Documentation update
- [x] 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

Applications can now look up a score or feedback record by its ID. If no
feedback record exists, the server returns `null`; it can also add
available author details to feedback.

## Summary

- Added `GET /observability/feedback/:feedbackId`. The route uses
existing observability authorization and returns `{ feedback: record }`
or `{ feedback: null }`.
- The feedback route adds author details when available. It returns HTTP
501 when the storage provider does not support single-feedback reads.
- Added `getScore(id)` and `getFeedback(id)` to the JavaScript client.
These methods encode IDs in the URL and use the client’s configured
request options.
- Added direct feedback lookups to in-memory, PostgreSQL, ClickHouse,
and DuckDB storage.
- Added response types, generated route metadata, API documentation,
tests, and changesets.

## Validation

Test and CI results: not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-06 10:23:52 +01:00
mastra-platform[bot]
2f93851c37
fix(core): make Agent.durable configure resumable streams only (#29503)
Co-authored-by: NikAiyer <nick.aiyer@gmail.com>
2026-11-05 11:32:10 -08:00
mastra-platform[bot]
a0068a9ad1
feat(core): resumable streams for every Agent (#28424)
> Opened by @user_01KNPFT2RPETZTEP15J3AEBA08

Originally stacked on
[#28416](https://github.com/mastra-ai/mastra/pull/28416), which has
merged. This PR now targets `main`.

## What

Any `Agent` can now have resumable streams, not only durable agents. A
run is published on `agent.stream.<runId>` with a replay cache, so:

- a client can reconnect after a disconnect,
- another reader can follow the run with `agent.observe(runId)`,
- any reader can stop it (`observe().abort()`,
`agent.abortRunStream(runId)`, or the abort-run route).

Durable execution (surviving process restarts) stays with `DurableAgent`
/ `EventedAgent` / `InngestAgent`, which keep publishing through the
same stream layer.

### Config

New `streams?: boolean | { pubsub, cache, shouldCache, cleanupTimeoutMs
}` on `Agent`.

- Omitted: on when the agent is registered on `Mastra`, off for
standalone agents.
- `false`: off. `{ cache: false }`: live only, no replay.
- With `durable`, `streams` keys override `durable` keys. `durable:
true` + `streams: false` keeps publishing, drops the replay cache, and
warns.

### Bus selection
- Registered agents (plain and `DurableAgent` on any engine) publish on
`mastra.pubsub`, so other processes sharing the PubSub and run-record
cache can observe and abort.
- Precedence: `streams.pubsub` > `durable.pubsub` > `mastra.pubsub`. The
evented engine still forces `mastra.pubsub` over an agent-level pubsub
and warns when they differ.
- Unregistered agents keep a private in-process `EventEmitterPubSub`.
- The replay cache wraps the shared bus once (existing `CachingPubSub`
reuse check), so nothing is double-published.

### Behaviour change

With streams on, closing the HTTP stream detaches the reader instead of
aborting the run. To stop a run explicitly, use `POST
/agents/:agentId/runs/:runId/abort`, which now works for plain agents
too (ownership-checked, including across servers sharing the PubSub and
run-record cache), or the thread abort route. `streams: false` keeps the
old behaviour.

## Commits

1. `8c8975ef` loop publishes chunks through a `streamPublisher`
(step-start, finish, CHUNK, SUSPENDED on close, ERROR if the stream ends
without a finish).
2. `f6d7dabf` `Agent.observe` reads the agent's bus;
`hasResumableStreams()` added. DurableAgent opts its inner agent out so
nothing is published twice.
3. `8b33a9d7` abort requests go over the control topic, so any reader on
the bus can stop a run.
4. `92a5a320` server: stream routes gate on `hasResumableStreams`,
observe reads a plain agent's bus, abort-run supports plain runs;
cleanup timers centralised on `AgentStreamBus.scheduleCleanup`.
5. `ff5456df` "Resumable streams" docs page, `Agent` reference entry,
changeset (core minor, server patch).
6. `24936904` registered `DurableAgent` on the default engine publishes
on `mastra.pubsub`. Before, if the bus was read before registration, it
stayed on the private bus and other instances never saw its runs.

## Rebase onto #28416 / main
- `loop/workflows/stream.ts` conflicted with #28157, which added a
`finalization` parameter to `workflowLoopStream`. Kept main's signature
and added `streamPublisher` alongside; snapshot finalization and
publishing both run.
- No textual conflict, but #28531 (follow-up to #28514) made stream
output a proxy, so `fullStream` overrides must call the base getter with
`this`. `Agent.observe` had the old pattern and failed with "Cannot read
private member #options"; main's fix is applied there (folded into
`f6d7dabf`). Reverting it fails both observe tests in
`agent-streams.test.ts`.

## Proof

Head `d2bd22d4`:
- Core `tsc -p tsconfig.build.json`, oxlint, oxfmt clean. `vitest run
src/agent/durable src/agent/streams
src/agent/__tests__/thread-stream-restart.test.ts` plus the
observe-approval-resume, observe-lifecycle and observe-reattach aimock
scenarios: 197 files, 1985 passed, 28 skipped, exit 0.
- Server `tsc` clean; `vitest run src/server/handlers`: 67 files, 2476
passed, 2 skipped, 1 todo.
- Inngest `tsc` clean; `test:unit` 103 passed, 2 failed. The same 2
tests ("stream/generate terminates when the opening event and error
event cannot be published") fail identically on `main` (`df76f896`,
rebuilt core).
- Docs: `remark --frail` and `oxfmt-mdx --check` clean.
- Observation spans suspension: new shared aimock scenario
`observe-approval-resume` on normal, durable, evented and fs engines. An
observer attached before and one attached during the approval wait both
receive the approved answer and `finish`; a fresh replay after
completion holds both segments; reconnecting after the suspension index
repeats nothing; the tool runs once; `onSuspended` fires once; a
cancelled reader leaves the run going.
- Request context: an unscoped Studio caller (auth mapper, Studio FGA,
no server FGA) can observe and abort; other tenants and unscoped
non-Studio callers still get 403; observe resolves the agent with the
request context.
- Shared ownership: each plain run writes a record
(`agent.run.<agentId>.<runId>`: agent, run, resource, thread,
running/suspended/finished) to the replay cache, or `mastra.serverCache`
when replay caching is off, before its first event. Suspended and
finished are written after the terminal event, the record is deleted
with the topic, and it has the run log's 24h TTL. Routes return 404 for
a missing, expired or evicted record and 503 when the cache can't be
read. Abort returns `aborted: true` only when the executing process
acknowledges the stop.
- Two real HTTP servers
(`pubsub/redis-streams/src/plain-run-cross-server.test.ts`: LibSQL file,
Redis Streams PubSub, RedisServerCache, SimpleAuth, aimock): owner
observes on B through suspend, approve on A, and finish; 403/401/404 on
both servers; abort through B confirmed by A; a parked run's abort is
`false`; expired and cleaned-up runs 404; ownership with `cache: false`.
Run with the durable/evented controls (`run-abort-cross-server`,
`observe-cross-process`): 20/20 in 3 consecutive runs. On the
pre-ownership commit the plain suite fails 8/8 (remote observe/abort
404).
- Mutation checks (each restored afterwards): re-adding `closeOnSuspend`
to plain observe fails the normal and fs scenarios; re-adding the HTTP
close on `suspended` fails the server test; dropping the request context
fails the Studio observe/abort and agent lookup tests; removing the
initial, suspended or delete record writes fails the record lifecycle
tests; removing the finished guard, the 503 handling or the
acknowledgement in the abort route fails their tests; acking an abort
that reached an ended run fails the new publisher test.
- No double publishing: the parity, durable-shared-bus and agent-streams
tests still pass (DurableAgent's inner agent keeps `streams: false`; the
replay cache wraps the shared bus once).

## Separate main-merge verification

Conflict resolution is isolated in
[50a9ef89](50a9ef8947),
after candidate `d2bd22d4`; no feature commits were rewritten.

- Merged-result focused core regression suites: 6 files, 37 tests
passed, covering parity, shared buses/run records, remote abort and
approval/resume observation.
- Complete merged-result server-handler suite: 68 files, 2,478 passed, 2
skipped, 1 todo. A separate real-TCP Hono/real-Memory authorization
matrix also passed 13/13, including the formerly failing Studio-only FGA
observe and abort contracts (without expected-failure markers).
- Type-aware oxlint and formatting passed on all 5 conflict-resolved
files.
- Full core/server typechecks are **not clean in the verification
checkout**. Swapping each package to unchanged `main` source in the same
installed dependency environment reproduces the same diagnostics (core
byte-identical; server identical after normalizing source-line
positions). These include AI SDK schema compatibility errors and missing
agent-builder artifacts; no additional diagnostics were introduced by
the conflict resolution.
- A broader core run passed 2,020 tests but exited nonzero: 5 suites
initially lacked the built internal LLM recorder; after building it, all
5 suites passed (24 tests). The crash-recovery worker still exhausted
its JavaScript heap after 8 of 10 tests. The broad run also reported the
baseline type errors above. This is **not** a clean full-core result.
- Follow-up `ec0bc59b` clears control and acknowledgement topics with
the finished run log; `35debe7a` and `920a094a` correct documentation.
Independent verification below includes the cleanup production change.

## Independent adversarial review

Verdict: **approve within the requested scope**, with no actionable
supported-flow defect found. No formal GitHub approval was posted. The
reviewed production head is `ec0bc59b32`;
the only subsequent change in `920a094a` is a checked docs sentence
distinguishing expired ownership from missing replay history.

Independent reviewer ran **343 passing tests**: 38 focused core, 280
server handlers, 8 real two-process TCP/Redis/LibSQL/AIMock cases, 16
public-API processor-safety probes, and 1 actual Redis cleanup probe.

- Redaction/tripwire bypass hypothesis did not reproduce on normal,
durable, evented or filesystem engines, with either immediate or
deferred initiating-stream consumption. Serialized observer frames
excluded the raw sensitive value; redaction replay matched the masked
caller output, and tripwires exposed no raw text. No processor redesign
was made.
- Actual Redis cleanup was tested after an acknowledged cross-node
abort: physical run, control, acknowledgement, counter/list and
ownership keys were first observed, then all ten run-associated keys
disappeared after configured cleanup. This verifies more than the added
clearTopic spy assertion.
- The reviewer used source aliases for the exact production sources in a
disposable checkout, including both child HTTP processes. They did not
independently validate the full build, Inngest, browser Studio Stop,
natural 24-hour expiry or load costs.

## Unverified

- Studio Stop button for thread-less plain runs: not exercised in a
browser.
- Cost: every registered agent publishes each chunk and writes an
ownership record. Not benchmarked.
- Natural 24h expiry: tested by deleting the record, not by waiting.
Merged main now honors the requested minimum TTL for indexed in-memory
logs. Entry-cap eviction can still shorten replay; docs were corrected
in `35debe7a`.
- Abort of a run whose executing process died: returns `aborted: false`
after the ack timeout; the run's record stays until its TTL.

## Assumptions

- InngestAgent keeps its own pubsub/cache resolution. Importing a new
core export would fail `check-core-imports` until core is released, so
no Inngest change or peer-range bump here (and no inngest changeset).
Follow-up after release.
- thread-stream-restart's "leaves nothing" assertion now ignores the
agent stream topic, since run events are kept for `cleanupTimeoutMs` by
design.

## Decisions (confirmed by Tony)

1. Registered `DurableAgent`s on the default engine use `mastra.pubsub`,
same as plain agents; unregistered ones keep a private bus.
2. Streams are on by default for agents registered on `Mastra` and off
for standalone agents; docs explain the cost and how to turn streams
off.
3. With streams on, HTTP disconnect detaches instead of aborting.

## Open question

The Superagent security scan flags (3): a client can start expensive
runs and disconnect, and nothing limits active or concurrent detached
runs. Options: accept and document, cap detached runs, or keep
abort-on-disconnect for HTTP-started runs.

Risk: medium-high — every registered agent now publishes, HTTP
disconnect no longer aborts plain runs, and observe/abort now authorize
plain runs from a shared cache record.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## ELI5

If someone disconnects while an agent is working, the agent can keep
running and save its updates so the reader can reconnect. Authorized
readers can also check on or stop a run; this does not add crash
recovery to plain agents.

## What changed

- Added configurable resumable streams for plain `Agent` runs. Streams
default to on for agents registered with `Mastra` and off for standalone
agents.
- Added `observe()` replay and live updates, including observation from
an event offset. Added abort support through `observe().abort()`,
`abortRunStream(runId)`, and server routes.
- When streams are enabled, an HTTP disconnect detaches the reader
instead of aborting the run. For plain agents, `streams: false` disables
publishing. Durable agents continue to publish; `streams: false`
disables their replay cache.
- Added run ownership records and authorization checks. Shared PubSub
and cache support observation and abort across servers. Unknown or
unverified runs return 404; cache-read failures return 503.
- Added run-ID claim checks. A run ID already owned by another resource
is rejected with `AGENT_RUN_ID_ALREADY_CLAIMED` and maps to HTTP 409.
Concurrent claims across processes may still overlap because the cache
has no compare-and-set operation.
- Added cleanup timers that do not keep the process alive. Cache TTL and
eviction can also limit event retention.
- Updated step bookkeeping to use the run’s original owner when
execution replaces its abort signal.
- Added documentation, tests, and a Redis/LibSQL cross-server
integration suite.

## Verification and open questions

The supplied context reports that the merged-result server-handler suite
passed 2,478 tests, with 2 skipped and 1 todo. It also reports real
two-server Redis/LibSQL tests, but provides no exact result count. Full
core and server typechecks were not clean; the reported diagnostics were
reproduced against unchanged `main`. A broader core run stopped after 8
of 10 tests when the crash-recovery worker exhausted its heap. Two
Inngest unit-test failures were also reported on `main`.

The author flagged that detached runs can continue without limits on
active or concurrent runs. Browser testing of Studio Stop for
thread-less plain runs, performance costs, natural 24-hour expiry, and
abort behavior after the executing process dies remain unverified. An
abort request cannot be confirmed if the process running the run is
unavailable.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: NikAiyer <nick.aiyer@gmail.com>
Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: review <review@local>
2026-11-04 17:29:16 -08:00
dane-ai-mastra[bot]
675caf0613
chore: version packages (alpha) (#29336)
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>
2026-11-04 14:40:27 -08:00
Eric Pinzur
8ad7773cd4
feat(observability): align signal writes and context modes (#29289) 2026-11-04 12:00:19 -08:00
Marvin Frachet
944d4bcb13
feat(mcp-apps-components): add prebuilt MCP Apps with a dashboard renderer (#29321)
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>
2026-11-04 10:41:58 -08:00
Eric Pinzur
a7c4069df2
fix(observability): require trace IDs on feedback and score POSTs (#29287)
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 -->
2026-11-04 15:25:20 +01:00
mastra-platform[bot]
aa6777693d
feat(core): load storage v2 workflow result steps lazily (#29362)
Co-authored-by: Tony Kovanen <rase-@users.noreply.github.com>
2026-11-04 07:32:39 +01:00
dane-ai-mastra[bot]
6e8dfcb83f chore: version - exit prerelease mode 2026-11-03 23:45:58 +00:00
dane-ai-mastra[bot]
4bc3aa672f
chore: version packages (alpha) (#29255)
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>
2026-11-03 13:59:38 -07:00
Dane - AI (Mastra)
3bdb4ec5f4
chore(deps): update build tools (major) (#29026)
> [!NOTE]
> This PR body was truncated due to platform limits.

This PR contains the following updates:

| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
| [@vitest/coverage-v8](https://vitest.dev/guide/coverage)
([source](https://redirect.github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8))
| pnpm.catalog.default | major | [`4.1.12` →
`5.0.5`](https://renovatebot.com/diffs/npm/@vitest%2fcoverage-v8/4.1.12/5.0.5)
| `5.1.0` |
| [@vitest/mocker@>=2.1.0
<4.1.12](https://redirect.github.com/vitest-dev/vitest/tree/main/packages/mocker)
([source](https://redirect.github.com/vitest-dev/vitest/tree/HEAD/packages/mocker))
| pnpm-workspace.overrides | major | [`4.1.12` →
`5.0.5`](https://renovatebot.com/diffs/npm/@vitest%2fmocker@>=2.1.0
<4.1.12/4.1.12/5.0.5) | `5.1.0` |
| [@vitest/ui](https://vitest.dev/guide/ui)
([source](https://redirect.github.com/vitest-dev/vitest/tree/HEAD/packages/ui))
| pnpm.catalog.default | major | [`4.1.12` →
`5.0.5`](https://renovatebot.com/diffs/npm/@vitest%2fui/4.1.12/5.0.5) |
`5.1.0` |
| [dotenv](https://redirect.github.com/motdotla/dotenv) |
devDependencies | major | [`^17.4.2` →
`^18.0.9`](https://renovatebot.com/diffs/npm/dotenv/17.4.2/18.0.9) | |
| [dotenv](https://redirect.github.com/motdotla/dotenv) |
devDependencies | major | [`17.4.2` →
`18.0.9`](https://renovatebot.com/diffs/npm/dotenv/17.4.2/18.0.9) | |
| [vitest](https://vitest.dev)
([source](https://redirect.github.com/vitest-dev/vitest/tree/HEAD/packages/vitest))
| devDependencies | major | [`^4.1.12` →
`^5.0.5`](https://renovatebot.com/diffs/npm/vitest/4.1.12/5.0.5) |
`5.1.0` |
| [vitest](https://vitest.dev)
([source](https://redirect.github.com/vitest-dev/vitest/tree/HEAD/packages/vitest))
| pnpm.catalog.default | major | [`4.1.12` →
`5.0.5`](https://renovatebot.com/diffs/npm/vitest/4.1.12/5.0.5) |
`5.1.0` |
| [vitest](https://vitest.dev)
([source](https://redirect.github.com/vitest-dev/vitest/tree/HEAD/packages/vitest))
| devDependencies | major | [`4.1.12` →
`5.0.5`](https://renovatebot.com/diffs/npm/vitest/4.1.12/5.0.5) |
`5.1.0` |
| [vitest@>=2.1.0 <4.1.12](https://vitest.dev)
([source](https://redirect.github.com/vitest-dev/vitest/tree/HEAD/packages/vitest))
| pnpm-workspace.overrides | major | [`4.1.12` →
`5.0.5`](https://renovatebot.com/diffs/npm/vitest@>=2.1.0
<4.1.12/4.1.12/5.0.5) | `5.1.0` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency
Dashboard](../issues/9505) for more information.

---

### Release Notes

<details>
<summary>vitest-dev/vitest (@&#8203;vitest/coverage-v8)</summary>

###
[`v5.0.5`](https://redirect.github.com/vitest-dev/vitest/releases/tag/v5.0.5)

[Compare
Source](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.4...v5.0.5)

#####    🐞 Bug Fixes

- Keep vite default `fs.deny` with api token file  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Claude Opus 5.5** in
[#&#8203;11578](https://redirect.github.com/vitest-dev/vitest/issues/11578)
[<samp>(28dc1)</samp>](28dc1edfb)
- Handle quoted file names in `--changed`  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11583](https://redirect.github.com/vitest-dev/vitest/issues/11583)
[<samp>(14921)</samp>](14921e962)
- Add `data` to the `import.meta.hot` stub  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11590](https://redirect.github.com/vitest-dev/vitest/issues/11590)
[<samp>(3a828)</samp>](3a8289ac3)
- Set `skip` in `skipIf`, ignore `undefined` options  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11591](https://redirect.github.com/vitest-dev/vitest/issues/11591)
[<samp>(d523a)</samp>](d523a15f2)
- Skip builtin loading in async leak detector  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11598](https://redirect.github.com/vitest-dev/vitest/issues/11598)
[<samp>(fe86a)</samp>](fe86a64c6)
- Keep the import frame in native loader errors  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11599](https://redirect.github.com/vitest-dev/vitest/issues/11599)
[<samp>(9697b)</samp>](9697b3894)
- Run hook cleanups when a later hook fails  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11605](https://redirect.github.com/vitest-dev/vitest/issues/11605)
[<samp>(6c5a4)</samp>](6c5a44720)
- Release mocks of finished test files  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11607](https://redirect.github.com/vitest-dev/vitest/issues/11607)
[<samp>(e9c3d)</samp>](e9c3d72f0)
- Abort all running tests on cancel  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11606](https://redirect.github.com/vitest-dev/vitest/issues/11606)
[<samp>(6621a)</samp>](6621a72d6)
- **browser**:
- Ignore synthetic pagehide events  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11582](https://redirect.github.com/vitest-dev/vitest/issues/11582)
[<samp>(ca081)</samp>](ca0813584)
- Run plugin buildStart on server creation  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11593](https://redirect.github.com/vitest-dev/vitest/issues/11593)
[<samp>(ea611)</samp>](ea611e44c)
- Drop late connections of closed sessions  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11600](https://redirect.github.com/vitest-dev/vitest/issues/11600)
[<samp>(f161e)</samp>](f161e6df2)
- Wait 30s for the browser to close  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11601](https://redirect.github.com/vitest-dev/vitest/issues/11601)
[<samp>(6498b)</samp>](6498b666a)
- Run global setup once with instances  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11596](https://redirect.github.com/vitest-dev/vitest/issues/11596)
[<samp>(8dd67)</samp>](8dd67c262)
- **reporter**:
- End reason `&#&#8203;39;failed&#&#8203;39;` on worker crash  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11568](https://redirect.github.com/vitest-dev/vitest/issues/11568)
[<samp>(6ae8e)</samp>](6ae8e89ff)

#####     [View changes on
GitHub](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.4...v5.0.5)

###
[`v5.0.4`](https://redirect.github.com/vitest-dev/vitest/releases/tag/v5.0.4)

[Compare
Source](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.3...v5.0.4)

#####    🚀 Features

- **experimental**:
- Tag cache directories with CACHEDIR.TAG  -  by
[@&#8203;lifeiscontent](https://redirect.github.com/lifeiscontent) in
[#&#8203;11461](https://redirect.github.com/vitest-dev/vitest/issues/11461)
[<samp>(a8ea3)</samp>](a8ea3c8fd)
- Support `test.ui.theme` option  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11499](https://redirect.github.com/vitest-dev/vitest/issues/11499)
[<samp>(1da66)</samp>](1da66405d)
- Highlight selector multiple matches in trace view  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Claude Opus 5.5** in
[#&#8203;11489](https://redirect.github.com/vitest-dev/vitest/issues/11489)
[<samp>(5abba)</samp>](5abba1e1b)
- Print how many tests were affected and a total when running
`--changed`  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11424](https://redirect.github.com/vitest-dev/vitest/issues/11424)
[<samp>(a2336)</samp>](a23368585)
- Add an option to cache dependencies instead of statically parsing them
 -  by [@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11515](https://redirect.github.com/vitest-dev/vitest/issues/11515)
[<samp>(c0601)</samp>](c06012ac8)
- Add fit and zoom controls to trace viewer  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Claude Opus 5.5** in
[#&#8203;11490](https://redirect.github.com/vitest-dev/vitest/issues/11490)
[<samp>(f5dd9)</samp>](f5dd99ed0)

#####    🐞 Bug Fixes

- Fail the run on git and location filter errors  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11430](https://redirect.github.com/vitest-dev/vitest/issues/11430)
[<samp>(30d03)</samp>](30d0304d2)
- Enable fsModuleCache by default  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11435](https://redirect.github.com/vitest-dev/vitest/issues/11435)
[<samp>(ad208)</samp>](ad208cc29)
- Track project files and mocks with --changed  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11432](https://redirect.github.com/vitest-dev/vitest/issues/11432)
[<samp>(b0f2b)</samp>](b0f2b3bb9)
- Refactor caching, fix `:` in project and change the shape of `results`
cache  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11453](https://redirect.github.com/vitest-dev/vitest/issues/11453)
[<samp>(9673c)</samp>](9673c49a4)
- Keep full `$` string values when `taskTitleValueFormatTruncate` is 0
 -  by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa),
**Hiroshi Ogawa** and **Claude Opus 5.5** in
[#&#8203;11485](https://redirect.github.com/vitest-dev/vitest/issues/11485)
[<samp>(4f7e1)</samp>](4f7e1799b)
- Resolve node builtins in client environments  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11417](https://redirect.github.com/vitest-dev/vitest/issues/11417)
[<samp>(56b31)</samp>](56b319ac6)
- Fix module graph builtin externals after
[#&#8203;11421](https://redirect.github.com/vitest-dev/vitest/issues/11421)
 -  by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa),
**Hiroshi Ogawa** and **Claude Opus 5.5** in
[#&#8203;11491](https://redirect.github.com/vitest-dev/vitest/issues/11491)
and
[#&#8203;11421](https://redirect.github.com/vitest-dev/vitest/issues/11421)
[<samp>(008e1)</samp>](008e184cb)
- Wrap module mocks during in-source testing  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11505](https://redirect.github.com/vitest-dev/vitest/issues/11505)
[<samp>(36d19)</samp>](36d19cb00)
- Handle line endings in snapshot  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11522](https://redirect.github.com/vitest-dev/vitest/issues/11522)
[<samp>(4c468)</samp>](4c468aa40)
- Respect root in projects  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11521](https://redirect.github.com/vitest-dev/vitest/issues/11521)
[<samp>(26642)</samp>](26642f793)
- Resolve mocks in directories with spaces  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11539](https://redirect.github.com/vitest-dev/vitest/issues/11539)
[<samp>(caaef)</samp>](caaef9416)
- **api**:
- Publish the api token atomically  -  by
[@&#8203;umairnawaz333](https://redirect.github.com/umairnawaz333) in
[#&#8203;11323](https://redirect.github.com/vitest-dev/vitest/issues/11323)
[<samp>(6f990)</samp>](6f990fef1)
- **browser**:
- Close the mock route interception race  -  by
[@&#8203;cplieger](https://redirect.github.com/cplieger) and
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;8339](https://redirect.github.com/vitest-dev/vitest/issues/8339)
and
[#&#8203;11083](https://redirect.github.com/vitest-dev/vitest/issues/11083)
[<samp>(d6620)</samp>](d6620fae6)
- Allow toHaveTextContent without arguments  -  by
[@&#8203;nomadical](https://redirect.github.com/nomadical) in
[#&#8203;11425](https://redirect.github.com/vitest-dev/vitest/issues/11425)
[<samp>(8ebcf)</samp>](8ebcf5f8a)
- Apply API options without browser config  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10852](https://redirect.github.com/vitest-dev/vitest/issues/10852)
[<samp>(ad055)</samp>](ad055837b)
- Preserve undefined command arguments  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) and
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11497](https://redirect.github.com/vitest-dev/vitest/issues/11497)
[<samp>(1576d)</samp>](1576d3d89)
- Wait for setup mocks before importing a test file  -  by
[@&#8203;kasperpeulen](https://redirect.github.com/kasperpeulen) in
[#&#8203;11520](https://redirect.github.com/vitest-dev/vitest/issues/11520)
[<samp>(b61d1)</samp>](b61d1ced3)
- Avoid extra scroll outside the iframe  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11523](https://redirect.github.com/vitest-dev/vitest/issues/11523)
[<samp>(662e8)</samp>](662e8a363)
- Run browser instances as workers  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11525](https://redirect.github.com/vitest-dev/vitest/issues/11525)
[<samp>(bf04b)</samp>](bf04b9ccc)
- ⚠️ This can degrade performance if you have a custom `maxWorkers`
setting. Previously, it was applied incorrectly and could lead to Vitest
using too many resources. For example, a lower number would still open
too many browsers. Fixing it means Vitest opens less instances by
default now.
- Open one cdp session per tester  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11542](https://redirect.github.com/vitest-dev/vitest/issues/11542)
[<samp>(69e63)</samp>](69e6369f6)
- Clean up unmocked and pending mocks  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11537](https://redirect.github.com/vitest-dev/vitest/issues/11537)
[<samp>(5c955)</samp>](5c9552173)
- **coverage**:
- V8 browser memory leak between test files  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11466](https://redirect.github.com/vitest-dev/vitest/issues/11466)
[<samp>(2297d)</samp>](2297d93a8)
- `allowExternal` fails to include uncovered files  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11513](https://redirect.github.com/vitest-dev/vitest/issues/11513)
[<samp>(4ef00)</samp>](4ef000a93)
- Filenames containing brackets incorrectly showing as uncovered  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11531](https://redirect.github.com/vitest-dev/vitest/issues/11531)
[<samp>(0fa80)</samp>](0fa80f53c)
- Istanbul coverage wrong when module transform warmups  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11529](https://redirect.github.com/vitest-dev/vitest/issues/11529)
[<samp>(9f61d)</samp>](9f61dcca2)
- **deps**:
- Update all non-major dependencies  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11167](https://redirect.github.com/vitest-dev/vitest/issues/11167)
[<samp>(c74e0)</samp>](c74e099a9)
- **expect**:
- Fix `Map` and `Set` deep equality in some assertions  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Claude Opus 5.5** in
[#&#8203;11402](https://redirect.github.com/vitest-dev/vitest/issues/11402)
[<samp>(b4e79)</samp>](b4e79fd7a)
- Check value in chai-style returned  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11500](https://redirect.github.com/vitest-dev/vitest/issues/11500)
[<samp>(1aca0)</samp>](1aca02a21)
- **mocker**:
- Fix native loader mocking edge cases  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11540](https://redirect.github.com/vitest-dev/vitest/issues/11540)
[<samp>(cd423)</samp>](cd423ba04)
- **pretty-format**:
- Support boxed symbols  -  by
[@&#8203;lehni](https://redirect.github.com/lehni) in
[#&#8203;11445](https://redirect.github.com/vitest-dev/vitest/issues/11445)
and
[#&#8203;11446](https://redirect.github.com/vitest-dev/vitest/issues/11446)
[<samp>(eba44)</samp>](eba44926e)
- **reporters**:
- Junit to strip ANSI sequences from all XML attributes  -  by
[@&#8203;meganemura](https://redirect.github.com/meganemura) and
**Claude Opus 5.5** in
[#&#8203;11407](https://redirect.github.com/vitest-dev/vitest/issues/11407)
[<samp>(e1a73)</samp>](e1a731470)
- **runner**:
- Don't cache failed fixture setups  -  by
[@&#8203;hamed-bavar](https://redirect.github.com/hamed-bavar) in
[#&#8203;11237](https://redirect.github.com/vitest-dev/vitest/issues/11237)
and
[#&#8203;11238](https://redirect.github.com/vitest-dev/vitest/issues/11238)
[<samp>(4ee66)</samp>](4ee66c021)
- **typecheck**:
- Use typescript pool in toTestSpecification  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11451](https://redirect.github.com/vitest-dev/vitest/issues/11451)
[<samp>(5f273)</samp>](5f2739e74)
- **ui**:
- Remove duplicate browser-open call opening two tabs  -  by
[@&#8203;feastyr69](https://redirect.github.com/feastyr69) in
[#&#8203;11356](https://redirect.github.com/vitest-dev/vitest/issues/11356)
and
[#&#8203;11358](https://redirect.github.com/vitest-dev/vitest/issues/11358)
[<samp>(d7e13)</samp>](d7e1315c1)
- Simplify explorer filtering + fix nested tests when search matches a
suite  -  by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa),
**Hiroshi Ogawa**, **Codex** and **Claude Opus 5.5** in
[#&#8203;11262](https://redirect.github.com/vitest-dev/vitest/issues/11262)
[<samp>(a627b)</samp>](a627be498)
- Store module graph once per environment  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Claude Opus 5.5** in
[#&#8203;11421](https://redirect.github.com/vitest-dev/vitest/issues/11421)
[<samp>(af903)</samp>](af903c65e)
- Mount index.html handler on the ui base path  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Claude Opus 5.5** in
[#&#8203;11517](https://redirect.github.com/vitest-dev/vitest/issues/11517)
[<samp>(1bc24)</samp>](1bc2495c7)
- Center split pane resize handle  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Claude Opus 5.5** in
[#&#8203;11506](https://redirect.github.com/vitest-dev/vitest/issues/11506)
[<samp>(e658b)</samp>](e658b9b6a)
- **vm**:
- Bind `this` to `module.exports`  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11504](https://redirect.github.com/vitest-dev/vitest/issues/11504)
[<samp>(b618a)</samp>](b618afd5c)

#####    🏎 Performance

- Reuse fsModuleCache when filtering by source  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11428](https://redirect.github.com/vitest-dev/vitest/issues/11428)
[<samp>(7ebd9)</samp>](7ebd95fdd)
- **spy**: Reset only mocks that were called or reconfigured  -  by
[@&#8203;johan-gorter](https://redirect.github.com/johan-gorter) and
**Claude Opus 5.5** in
[#&#8203;11197](https://redirect.github.com/vitest-dev/vitest/issues/11197)
[<samp>(28ef9)</samp>](28ef93df2)

#####     [View changes on
GitHub](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.3...v5.0.4)

###
[`v5.0.3`](https://redirect.github.com/vitest-dev/vitest/releases/tag/v5.0.3)

[Compare
Source](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.2...v5.0.3)

#####    🐞 Bug Fixes

- Isolate `result.status` between `repeats` runs  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Codex (GPT-6)** in
[#&#8203;11218](https://redirect.github.com/vitest-dev/vitest/issues/11218)
[<samp>(5dbeb)</samp>](5dbebe9e3)
- Don't print an interceptor warning in browser mode  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11377](https://redirect.github.com/vitest-dev/vitest/issues/11377)
[<samp>(15cc0)</samp>](15cc006aa)
- Don't retry when `test.fails` expectedly failed  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Codex (GPT-6)** in
[#&#8203;11219](https://redirect.github.com/vitest-dev/vitest/issues/11219)
[<samp>(b2458)</samp>](b24585f08)
- Scope cache key generators to projects  -  by
[@&#8203;ecoyoung](https://redirect.github.com/ecoyoung) in
[#&#8203;11281](https://redirect.github.com/vitest-dev/vitest/issues/11281)
and
[#&#8203;11301](https://redirect.github.com/vitest-dev/vitest/issues/11301)
[<samp>(92ba7)</samp>](92ba7fc1d)
- **browser**:
- Delay server `listen` until tests start running  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11366](https://redirect.github.com/vitest-dev/vitest/issues/11366)
[<samp>(7d8ed)</samp>](7d8ed3e9b)
- Check mock path boundaries  -  by
[@&#8203;saryn17](https://redirect.github.com/saryn17), **Ryosei Sato**
and [@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11361](https://redirect.github.com/vitest-dev/vitest/issues/11361)
and
[#&#8203;11362](https://redirect.github.com/vitest-dev/vitest/issues/11362)
[<samp>(1c388)</samp>](1c3888bce)
- Keep config of browser-consumed environments  -  by
[@&#8203;kasperpeulen](https://redirect.github.com/kasperpeulen) and
**Claude** in
[#&#8203;11378](https://redirect.github.com/vitest-dev/vitest/issues/11378)
[<samp>(aafc0)</samp>](aafc0996f)
- Ignore page crash while cancelling  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11386](https://redirect.github.com/vitest-dev/vitest/issues/11386)
[<samp>(7c367)</samp>](7c36748fa)
- `toMatchScreenshot` uses wrong reference on retried tests  -  by
[@&#8203;macarie](https://redirect.github.com/macarie) in
[#&#8203;11393](https://redirect.github.com/vitest-dev/vitest/issues/11393)
[<samp>(c22ab)</samp>](c22aba992)
- **cache**:
- Revalidate imports of cached modules  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11381](https://redirect.github.com/vitest-dev/vitest/issues/11381)
[<samp>(38f98)</samp>](38f98855f)
- **deps**:
- Pin `why-is-node-running` to `3.2.1` to avoid users running into
`ERR_PNPM_TRUST_DOWNGRADE`  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11403](https://redirect.github.com/vitest-dev/vitest/issues/11403)
[<samp>(f6c9a)</samp>](f6c9a4977)
- **expect**:
- Pass current equality testers to `expect.extend` asymmetric matchers
 -  by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa),
**Hiroshi Ogawa** and **Claude** in
[#&#8203;11401](https://redirect.github.com/vitest-dev/vitest/issues/11401)
[<samp>(3e794)</samp>](3e794a96b)
- **jsdom**:
- Support Blob on jsdom 30.1  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11379](https://redirect.github.com/vitest-dev/vitest/issues/11379)
[<samp>(6c49b)</samp>](6c49b7197)
- **pool**:
- Preserve unique pool ids when `groupOrder` is set  -  by
[@&#8203;mtorp](https://redirect.github.com/mtorp) in
[#&#8203;11392](https://redirect.github.com/vitest-dev/vitest/issues/11392)
[<samp>(50312)</samp>](50312ebb4)
- **ui**:
- Split-pane handle overlapping iframe  -  by
[@&#8203;macarie](https://redirect.github.com/macarie) in
[#&#8203;11221](https://redirect.github.com/vitest-dev/vitest/issues/11221)
[<samp>(f91db)</samp>](f91db0dfd)
- **vitest**:
- Remove root temp dir on close  -  by
[@&#8203;abhinav-phi](https://redirect.github.com/abhinav-phi) in
[#&#8203;11248](https://redirect.github.com/vitest-dev/vitest/issues/11248)
[<samp>(7c711)</samp>](7c7119cf7)
- **vm**:
- Do not optimize deps from index.html  -  by
[@&#8203;ezefernandezyf](https://redirect.github.com/ezefernandezyf),
**Hiroshi Ogawa** and **Codex (GPT-6)** in
[#&#8203;11329](https://redirect.github.com/vitest-dev/vitest/issues/11329)
and
[#&#8203;11360](https://redirect.github.com/vitest-dev/vitest/issues/11360)
[<samp>(caf28)</samp>](caf2887de)
- Don't reuse scripts across vite environments  -  by
[@&#8203;MO2k4](https://redirect.github.com/MO2k4), **Martin Oehlert**
and **Claude** in
[#&#8203;11395](https://redirect.github.com/vitest-dev/vitest/issues/11395)
[<samp>(346d3)</samp>](346d3896b)

#####     [View changes on
GitHub](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.2...v5.0.3)

###
[`v5.0.2`](https://redirect.github.com/vitest-dev/vitest/releases/tag/v5.0.2)

[Compare
Source](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.1...v5.0.2)

#####    🐞 Bug Fixes

- Bind `process` in case global is overwritten  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11343](https://redirect.github.com/vitest-dev/vitest/issues/11343)
[<samp>(0b792)</samp>](0b79231ad)
- **detect-async-leaks**:
- Ignore `process.stdio` handles  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11333](https://redirect.github.com/vitest-dev/vitest/issues/11333)
[<samp>(0fd6b)</samp>](0fd6b9790)
- **expect**:
- Fix `toMatchObject` with asymmetric matchers  -  by
[@&#8203;ShreeBohara](https://redirect.github.com/ShreeBohara), **Claude
Opus 5**, [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa),
**Hiroshi Ogawa** and **Codex (GPT-5)** in
[#&#8203;11100](https://redirect.github.com/vitest-dev/vitest/issues/11100)
[<samp>(42523)</samp>](42523289e)
- **jsdom**:
- Fix `Request` with `Blob` body on jsdom 28+  -  by
[@&#8203;harshit-d3v](https://redirect.github.com/harshit-d3v) in
[#&#8203;11295](https://redirect.github.com/vitest-dev/vitest/issues/11295)
[<samp>(d1c3e)</samp>](d1c3ecc93)
- **reporter**:
- `agent` to respect `--silent`  -  by
[@&#8203;Raj4478](https://redirect.github.com/Raj4478) and
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11271](https://redirect.github.com/vitest-dev/vitest/issues/11271)
[<samp>(5b95e)</samp>](5b95efb6d)
- **reporters**:
- Handle concurrent `createReport` calls  -  by
[@&#8203;7rulnik](https://redirect.github.com/7rulnik) in
[#&#8203;11278](https://redirect.github.com/vitest-dev/vitest/issues/11278)
[<samp>(e8e55)</samp>](e8e556ff7)
- `hanging-process` to use ESM entrypoint  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;11316](https://redirect.github.com/vitest-dev/vitest/issues/11316)
[<samp>(4e91e)</samp>](4e91e5668)
- **spy**:
- Fix stack overflow when spying `Set.prototype.add`  -  by
[@&#8203;fengmk2](https://redirect.github.com/fengmk2) in
[#&#8203;11299](https://redirect.github.com/vitest-dev/vitest/issues/11299)
[<samp>(a0a93)</samp>](a0a939653)
- **ui**:
- Persist authentication cookie beyond current browser session  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **OpenCode (gpt-5.6-sol)** in
[#&#8203;11066](https://redirect.github.com/vitest-dev/vitest/issues/11066)
[<samp>(f8819)</samp>](f88195e16)

#####     [View changes on
GitHub](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.1...v5.0.2)

###
[`v5.0.1`](https://redirect.github.com/vitest-dev/vitest/releases/tag/v5.0.1)

[Compare
Source](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.0...v5.0.1)

#####    🚀 Features

- **ui**:
- Move trace attempts selector to viewer header  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Codex** in
[#&#8203;11189](https://redirect.github.com/vitest-dev/vitest/issues/11189)
[<samp>(5dc4b)</samp>](5dc4b5c92)
- Add focused trace view layout mode  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa**, **OpenCode (gpt-5.6-sol)** and **Codex** in
[#&#8203;11190](https://redirect.github.com/vitest-dev/vitest/issues/11190)
[<samp>(376dc)</samp>](376dc3bc1)

#####    🐞 Bug Fixes

- Exit 1 when vitest list fails collection  -  by
[@&#8203;hamed-bavar](https://redirect.github.com/hamed-bavar) in
[#&#8203;11145](https://redirect.github.com/vitest-dev/vitest/issues/11145)
and
[#&#8203;11146](https://redirect.github.com/vitest-dev/vitest/issues/11146)
[<samp>(6108b)</samp>](6108b8197)
- Keep parse error details in static collection  -  by
[@&#8203;hamed-bavar](https://redirect.github.com/hamed-bavar) in
[#&#8203;11150](https://redirect.github.com/vitest-dev/vitest/issues/11150)
and
[#&#8203;11151](https://redirect.github.com/vitest-dev/vitest/issues/11151)
[<samp>(7c818)</samp>](7c818153a)
- Avoid recursive prototype in automocking  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11195](https://redirect.github.com/vitest-dev/vitest/issues/11195)
[<samp>(99fc5)</samp>](99fc52591)
- Prevent false Vitest import resolution  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11196](https://redirect.github.com/vitest-dev/vitest/issues/11196)
[<samp>(b426c)</samp>](b426c1976)
- Keep metadata file when clearing the cache  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11199](https://redirect.github.com/vitest-dev/vitest/issues/11199)
[<samp>(73614)</samp>](73614654a)
- Correct typos in error message and comments  -  by
[@&#8203;shinji00222](https://redirect.github.com/shinji00222) and
**Shinji** in
[#&#8203;11187](https://redirect.github.com/vitest-dev/vitest/issues/11187)
[<samp>(115c3)</samp>](115c3f6d2)
- Resolve ResolvedConfig exactOptionalPropertyTypes errors  -  by
[@&#8203;LukeAbby](https://redirect.github.com/LukeAbby) in
[#&#8203;11175](https://redirect.github.com/vitest-dev/vitest/issues/11175)
[<samp>(498fb)</samp>](498fbe922)
- Share the server on self-referencing `extends`  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11034](https://redirect.github.com/vitest-dev/vitest/issues/11034)
[<samp>(23dda)</samp>](23dda738c)
- Warn when deprecated `deps.optimizer.web` is used  -  by
[@&#8203;im10furry](https://redirect.github.com/im10furry) in
[#&#8203;11214](https://redirect.github.com/vitest-dev/vitest/issues/11214)
[<samp>(2ce29)</samp>](2ce29d5fa)
- **browser**:
- Avoid double quotes in `config.define`  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11198](https://redirect.github.com/vitest-dev/vitest/issues/11198)
[<samp>(972e2)</samp>](972e24bab)
- **doctor**:
- Measure vm pools for custom environments  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11212](https://redirect.github.com/vitest-dev/vitest/issues/11212)
[<samp>(91ab1)</samp>](91ab1588c)
- **expect**:
- Correct return value in `toMatchAriaSnapshot`  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11208](https://redirect.github.com/vitest-dev/vitest/issues/11208)
[<samp>(c119b)</samp>](c119be016)
- **fakeTimers**:
- Force `queueMicrotask` and `nextTick` in `toNotFake`  -  by
[@&#8203;kingmakeruix](https://redirect.github.com/kingmakeruix),
**kingmakeruix**, **Hiroshi Ogawa**, **Codex** and
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) in
[#&#8203;11261](https://redirect.github.com/vitest-dev/vitest/issues/11261)
[<samp>(a47d7)</samp>](a47d7908f)
- **snapshot**:
- Report obsolete keys next to skipped tests  -  by
[@&#8203;hamed-bavar](https://redirect.github.com/hamed-bavar),
**Hiroshi Ogawa** and **OpenCode (gpt-5.6-sol)** in
[#&#8203;11157](https://redirect.github.com/vitest-dev/vitest/issues/11157)
and
[#&#8203;11158](https://redirect.github.com/vitest-dev/vitest/issues/11158)
[<samp>(17e2b)</samp>](17e2b22dd)
- **types**:
- Make public declarations self-contained  -  by
[@&#8203;ZoeySigel](https://redirect.github.com/ZoeySigel) in
[#&#8203;11141](https://redirect.github.com/vitest-dev/vitest/issues/11141)
[<samp>(45546)</samp>](455466c16)
- **ui**:
- Fix collapse/expand suite with file name search  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Codex** in
[#&#8203;11260](https://redirect.github.com/vitest-dev/vitest/issues/11260)
[<samp>(0a712)</samp>](0a7122daa)
- Fix explorer file summary count  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa**, **OpenCode (gpt-5.6-sol)** and **Codex** in
[#&#8203;11125](https://redirect.github.com/vitest-dev/vitest/issues/11125)
[<samp>(05982)</samp>](05982297d)
- **utils**:
- Fix `deepMerge` to handle prototype  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **Codex** in
[#&#8203;11215](https://redirect.github.com/vitest-dev/vitest/issues/11215)
[<samp>(4944c)</samp>](4944cf498)

#####     [View changes on
GitHub](https://redirect.github.com/vitest-dev/vitest/compare/v5.0.0...v5.0.1)

###
[`v5.0.0`](https://redirect.github.com/vitest-dev/vitest/releases/tag/v5.0.0)

[Compare
Source](https://redirect.github.com/vitest-dev/vitest/compare/v4.1.12...v5.0.0)

Vitest 5 is officially out! This release focuses on performance and
brings a lot of new features while fixing long-standing bugs. See our
[blog post](https://vitest.dev/blog/vitest-5.html) for the official
announcement.

#####    🚨 Breaking Changes

- Replace `loupe.inspect` with pretty-format  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Claude Opus
5 (1M context)** and **OpenAI Codex** in
[#&#8203;9609](https://redirect.github.com/vitest-dev/vitest/issues/9609)
[<samp>(3f802)</samp>](3f802da4b)
- Remove quotes from string values in `test.for/each` title `$` variable
(take 2)  -  by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa)
in
[#&#8203;10170](https://redirect.github.com/vitest-dev/vitest/issues/10170)
[<samp>(04d37)</samp>](04d37e9d7)
- Default `attachmentsDir` from `.vitest-attachements/` to
`.vitest/attachments/`  -  by
[@&#8203;MdSadiqMd](https://redirect.github.com/MdSadiqMd) in
[#&#8203;10186](https://redirect.github.com/vitest-dev/vitest/issues/10186)
[<samp>(1ba73)</samp>](1ba7338c3)
- Remove `sequential` test/suite options in favor of `concurrent`  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) and **OpenAI
Codex** in
[#&#8203;10198](https://redirect.github.com/vitest-dev/vitest/issues/10198)
[<samp>(9229f)</samp>](9229f2edc)
- Represent locator as an object instead of a string  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10212](https://redirect.github.com/vitest-dev/vitest/issues/10212)
[<samp>(80f07)</samp>](80f07edf6)
- Inline `expect` package  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10221](https://redirect.github.com/vitest-dev/vitest/issues/10221)
[<samp>(ad162)</samp>](ad16223e7)
- Remove deprecated entry points  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10222](https://redirect.github.com/vitest-dev/vitest/issues/10222)
[<samp>(994c6)</samp>](994c6ddb9)
- Require Node.js 22 and Vite 6.4  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10178](https://redirect.github.com/vitest-dev/vitest/issues/10178)
[<samp>(38762)</samp>](3876283e8)
- Fail `expect.poll` when function didn't resolve in time  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) and **OpenAI
Codex** in
[#&#8203;10233](https://redirect.github.com/vitest-dev/vitest/issues/10233)
[<samp>(4df04)</samp>](4df048c11)
- Throw an error if hoistable methods are outside the top level scope
 -  by [@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10460](https://redirect.github.com/vitest-dev/vitest/issues/10460)
[<samp>(d0b4f)</samp>](d0b4fddcb)
- `toHaveTextContent` is strict, add `toMatchTextContent` as alternative
 -  by [@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10473](https://redirect.github.com/vitest-dev/vitest/issues/10473)
[<samp>(18f30)</samp>](18f303079)
- Don't lookup config file from ancestor directories  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **OpenAI
Codex** and **Hiroshi Ogawa** in
[#&#8203;10428](https://redirect.github.com/vitest-dev/vitest/issues/10428)
[<samp>(945d9)</samp>](945d9090e)
- Inline `@vitest/runner` package, do not publish it anymore  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10511](https://redirect.github.com/vitest-dev/vitest/issues/10511)
[<samp>(6d6e4)</samp>](6d6e46b1e)
- Allow mutating happy-dom/jsdom window object  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **OpenAI Codex** in
[#&#8203;10373](https://redirect.github.com/vitest-dev/vitest/issues/10373)
[<samp>(206e8)</samp>](206e8cff8)
- Expose `concurrencyId`/`workerId` on TestModule's diagnostics, make id
1-based  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10516](https://redirect.github.com/vitest-dev/vitest/issues/10516)
[<samp>(bdd98)</samp>](bdd985433)
- Add `screenshotDirectory` config to `browser.expect.toMatchScreenshot`
 -  by [@&#8203;macarie](https://redirect.github.com/macarie) in
[#&#8203;10592](https://redirect.github.com/vitest-dev/vitest/issues/10592)
[<samp>(a60de)</samp>](a60ded0fb)
- Update `@sinonjs/fake-timers` and support mocking `Temporal`  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **OpenCode (gpt-5.6-sol)** in
[#&#8203;10654](https://redirect.github.com/vitest-dev/vitest/issues/10654)
[<samp>(f8b15)</samp>](f8b1532fe)
- Remove webdriverio package  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10675](https://redirect.github.com/vitest-dev/vitest/issues/10675)
[<samp>(5fed6)</samp>](5fed68f72)
- Clear mocks by default before each test  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10613](https://redirect.github.com/vitest-dev/vitest/issues/10613)
[<samp>(0f646)</samp>](0f6463bf2)
- Don't emit localStorage warnings on Node 26, fail gracefully when
worker fails to start  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10293](https://redirect.github.com/vitest-dev/vitest/issues/10293)
[<samp>(334ed)</samp>](334edef92)
- Separate config resolution from the server creation  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10554](https://redirect.github.com/vitest-dev/vitest/issues/10554)
[<samp>(1c0ec)</samp>](1c0ec3444)
- Inline projects extend the root config by default  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10750](https://redirect.github.com/vitest-dev/vitest/issues/10750)
[<samp>(fec00)</samp>](fec001ad3)
- Enable mocking Temporal without fake timers  -  by
[@&#8203;fabon-f](https://redirect.github.com/fabon-f), **Hiroshi
Ogawa** and **OpenCode (gpt-5.6-sol)** in
[#&#8203;10757](https://redirect.github.com/vitest-dev/vitest/issues/10757)
[<samp>(ac2d4)</samp>](ac2d46b42)
- Support nested projects  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10846](https://redirect.github.com/vitest-dev/vitest/issues/10846)
[<samp>(ec367)</samp>](ec367cf2a)
- Use `>` as separator in `-t`, calculate `only` once  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10686](https://redirect.github.com/vitest-dev/vitest/issues/10686)
[<samp>(a0b20)</samp>](a0b20bc86)
- Fail the test when an asynchronous assertion is not awaited  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10868](https://redirect.github.com/vitest-dev/vitest/issues/10868)
[<samp>(86d4a)</samp>](86d4a9da9)
- Share the Vite server between inline projects  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10848](https://redirect.github.com/vitest-dev/vitest/issues/10848)
[<samp>(d87c9)</samp>](d87c96ee4)
- Parse files statically in vitest list by default  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11088](https://redirect.github.com/vitest-dev/vitest/issues/11088)
[<samp>(51e94)</samp>](51e949416)
- **benchmark**:
- Rewrite the public API  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10113](https://redirect.github.com/vitest-dev/vitest/issues/10113)
[<samp>(19f6e)</samp>](19f6e8947)
- **browser**:
- Iframe scale  -  by
[@&#8203;macarie](https://redirect.github.com/macarie) in
[#&#8203;9745](https://redirect.github.com/vitest-dev/vitest/issues/9745)
[<samp>(b6398)</samp>](b639852cc)
- Enable `locators.exact` by default  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10430](https://redirect.github.com/vitest-dev/vitest/issues/10430)
[<samp>(e2032)</samp>](e203202f9)
- Require `sessionId` for orchestrator html request  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **OpenAI Codex** in
[#&#8203;10522](https://redirect.github.com/vitest-dev/vitest/issues/10522)
[<samp>(79b7d)</samp>](79b7d8fcc)
- Save failure screenshots in `attachmentsDir`  -  by
[@&#8203;macarie](https://redirect.github.com/macarie) in
[#&#8203;10917](https://redirect.github.com/vitest-dev/vitest/issues/10917)
[<samp>(3b5bb)</samp>](3b5bbd8b4)
- **coverage**:
- `include/exclude` globs too eager  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;9818](https://redirect.github.com/vitest-dev/vitest/issues/9818)
[<samp>(edacb)</samp>](edacb0fd4)
- Allow `thresholds.perFile` to accept an object  -  by
[@&#8203;vladlenskiy](https://redirect.github.com/vladlenskiy) and
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;10190](https://redirect.github.com/vitest-dev/vitest/issues/10190)
[<samp>(13b78)</samp>](13b78d98b)
- **expect**:
- Fix `toThrow("")` behavior by reverting
[#&#8203;6710](https://redirect.github.com/vitest-dev/vitest/issues/6710)
 -  by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) in
[#&#8203;9643](https://redirect.github.com/vitest-dev/vitest/issues/9643)
and
[#&#8203;6710](https://redirect.github.com/vitest-dev/vitest/issues/6710)
[<samp>(6c3e4)</samp>](6c3e4bdbf)
- **mocker**:
- Deserialize automock as automock  -  by
[@&#8203;nami8824](https://redirect.github.com/nami8824) in
[#&#8203;10192](https://redirect.github.com/vitest-dev/vitest/issues/10192)
[<samp>(2f892)</samp>](2f892712d)
- **reporters**:
- `blob` reporter and `--merge-reports` default to `.vitest/blob/`  - 
by [@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;10232](https://redirect.github.com/vitest-dev/vitest/issues/10232)
[<samp>(d22b0)</samp>](d22b029ae)
- Write json and junit reporter output files to `.vitest` by default  - 
by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa**, **OpenCode (gpt-5.6-sol)** and
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;10621](https://redirect.github.com/vitest-dev/vitest/issues/10621)
[<samp>(58577)</samp>](58577290a)
- **spy**:
- Preserve class mock prototype methods on instances  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10910](https://redirect.github.com/vitest-dev/vitest/issues/10910)
[<samp>(6093d)</samp>](6093d764a)
- **types**:
- Add better promise support in expects and matchers  -  by
[@&#8203;samchungy](https://redirect.github.com/samchungy) and
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;8266](https://redirect.github.com/vitest-dev/vitest/issues/8266)
[<samp>(41f55)</samp>](41f551bce)
- **ui**:
- Harden UI API access  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi
Ogawa** and **OpenAI Codex** in
[#&#8203;10583](https://redirect.github.com/vitest-dev/vitest/issues/10583)
[<samp>(4c26d)</samp>](4c26d7675)
- Change html reporter default output to `.vitest`  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) and **Hiroshi
Ogawa** in
[#&#8203;10620](https://redirect.github.com/vitest-dev/vitest/issues/10620)
[<samp>(29c36)</samp>](29c364d50)

#####    🚀 Features

- Add `createReport` and `.vitest` report directory convention  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;9993](https://redirect.github.com/vitest-dev/vitest/issues/9993)
[<samp>(72a6d)</samp>](72a6dc257)
- Expose default reporters through `configDefaults.reporters`  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) and **Claude
Opus 5 (1M context)** in
[#&#8203;10219](https://redirect.github.com/vitest-dev/vitest/issues/10219)
[<samp>(083f6)</samp>](083f6bdd6)
- Support merge reports for non-sharded multi-environment runs (take 2)
 -  by [@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa),
**Claude Opus 5 (1M context)**, **OpenAI Codex** and
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;10031](https://redirect.github.com/vitest-dev/vitest/issues/10031)
[<samp>(e60b2)</samp>](e60b2f49e)
- Add `logger.formatError`  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) and **OpenAI
Codex** in
[#&#8203;10268](https://redirect.github.com/vitest-dev/vitest/issues/10268)
[<samp>(2c5f3)</samp>](2c5f3ee2f)
- Support typescript build mode  -  by
[@&#8203;lishaduck](https://redirect.github.com/lishaduck) in
[#&#8203;9870](https://redirect.github.com/vitest-dev/vitest/issues/9870)
[<samp>(106da)</samp>](106da5896)
- Add toggable `injectCjsGlobals` option  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10709](https://redirect.github.com/vitest-dev/vitest/issues/10709)
[<samp>(82671)</samp>](826714ece)
- Promote fsModuleCache to a top-level option  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10734](https://redirect.github.com/vitest-dev/vitest/issues/10734)
[<samp>(78ed7)</samp>](78ed73afd)
- Support non-ascii characters in `for/each` title placeholders  -  by
[@&#8203;k-yle](https://redirect.github.com/k-yle) in
[#&#8203;10773](https://redirect.github.com/vitest-dev/vitest/issues/10773)
[<samp>(15e0a)</samp>](15e0af953)
- Report the duration breakdown as percentages  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) and
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in
[#&#8203;10820](https://redirect.github.com/vitest-dev/vitest/issues/10820)
[<samp>(c67d2)</samp>](c67d296f4)
- Promote parseSpecifications out of experimental  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11087](https://redirect.github.com/vitest-dev/vitest/issues/11087)
[<samp>(b628c)</samp>](b628cb680)
- Promote clearCache out of experimental  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;11086](https://redirect.github.com/vitest-dev/vitest/issues/11086)
[<samp>(d4fe1)</samp>](d4fe1986f)
- **api**:
- Expose logs recorded during the test  -  by
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10277](https://redirect.github.com/vitest-dev/vitest/issues/10277)
[<samp>(cba20)</samp>](cba2036a1)
- **benchmark**:
- Add pluggable benchmark provider API  -  by
[@&#8203;GuillaumeLagrange](https://redirect.github.com/GuillaumeLagrange)
and [@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10799](https://redirect.github.com/vitest-dev/vitest/issues/10799)
[<samp>(86c70)</samp>](86c700ed8)
- **browser**:
- Export aria tree utils  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) in
[#&#8203;10171](https://redirect.github.com/vitest-dev/vitest/issues/10171)
[<samp>(c3423)</samp>](c3423014c)
- Support dom snapshot trace view  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa), **Claude Opus
5 (1M context)** and **OpenAI Codex** in
[#&#8203;10102](https://redirect.github.com/vitest-dev/vitest/issues/10102)
[<samp>(7eddd)</samp>](7eddd273d)
- Provide project reference in `ToMatchScreenshotResolvePath`  -  by
[@&#8203;macarie](https://redirect.github.com/macarie) and
[@&#8203;sheremet-va](https://redirect.github.com/sheremet-va) in
[#&#8203;10138](https://redirect.github.com/vitest-dev/vitest/issues/10138)
[<samp>(16654)</samp>](166544e39)
- Show aria tree on locator element error  -  by
[@&#8203;hi-ogawa](https://redirect.github.com/hi-ogawa) and **OpenAI
Codex** in
[#&#8203;10257](https://redirect.github.com/vitest-dev/vitest/issues/10257)
[<samp>(04f04)</samp>](04f04cdd1)
- Support custom `kind` in `page.mark`  -  by
[@&#8203;AriPerkkio](https://redirect.github.com/AriPerkkio) in

> [!IMPORTANT]
> ✂ PR body was truncated to here.


</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - "before 6am every weekday"
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config
help](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend Renovate
CLI](https://redirect.github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xOTguMiIsInVwZGF0ZWRJblZlciI6IjQ0LjIwNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0aW9uIl19-->

---------

Co-authored-by: wardpeet <ward@coding-tech.com>
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-11-03 20:18:21 +01:00
Arthur Fiorette
de1b638b2f
fix(server): give each Mastra instance its own agent-builder workflows (#29253) 2026-11-03 15:26:49 -03:00