This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and publish to npm
yourself or [setup this action to publish
automatically](https://github.com/changesets/action#with-publishing). If
you're not ready to do a release yet, that's fine, whenever you add more
changesets to main, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
`main` is currently in **pre mode** so this branch has prereleases
rather than normal releases. If you want to exit prereleases, run
`changeset pre exit` on `main`.
⚠️⚠️⚠️⚠️⚠️⚠️
# Releases
> The changelog information of each package has been omitted from this
message, as the content exceeds the size limit.
## @mastra/auth-auth0@1.3.0-alpha.0
## @mastra/auth-clerk@1.4.0-alpha.0
## @mastra/auth-okta@0.3.0-alpha.0
## @mastra/auth-supabase@1.2.0-alpha.0
## @mastra/client-js@1.60.0-alpha.13
## @mastra/auth@1.2.0-alpha.0
## @mastra/core@1.83.0-alpha.13
## @mastra/playground-ui@69.0.0-alpha.15
## @mastra/rag@2.8.0-alpha.3
## @mastra/server@1.83.0-alpha.13
## @mastra/server-adapters-test-suite@0.3.0-alpha.5
## @mastra/auth-better-auth@1.1.11-alpha.2
## @mastra/auth-cloud@1.2.9-alpha.0
## @mastra/auth-neon@0.3.6-alpha.1
## @mastra/auth-workos@1.6.9-alpha.0
## @mastra/discord@1.3.4-alpha.0
## @mastra/react@1.15.0-alpha.13
## @mastra/deployer-cloud@1.83.0-alpha.13
## @mastra/deployer-cloudflare@1.2.42-alpha.3
## @mastra/deployer-netlify@1.2.42-alpha.1
## @mastra/deployer-sandbox@0.3.27-alpha.1
## @mastra/deployer-vercel@1.2.42-alpha.1
## @mastra/longmemeval@1.1.42-alpha.13
## @mastra/opencode@0.1.42-alpha.13
## @mastra/factory@0.28.0-alpha.15
## create-factory@0.4.3-alpha.15
## @mastra/code-sdk@1.19.0-alpha.15
## mastracode@0.50.0-alpha.14
## @mastra/agent-builder@1.2.1-alpha.5
## mastra@1.39.0-alpha.15
## @mastra/connect@1.4.0-alpha.6
## @mastra/deployer@1.83.0-alpha.13
## @mastra/editor@0.17.1-alpha.7
## @mastra/mcp@2.9.0-alpha.5
## @mastra/mcp-docs-server@1.3.13-alpha.17
## @mastra/memory@1.41.1-alpha.5
## @mastra/schema-compat@1.4.0-alpha.2
## @mastra/elysia@0.1.23-alpha.13
## @mastra/express@1.5.27-alpha.13
## @mastra/fastify@1.5.27-alpha.13
## @mastra/hono@1.7.25-alpha.13
## @mastra/koa@1.7.27-alpha.13
## @mastra/nestjs@0.3.0-alpha.13
## @mastra/next@0.2.41-alpha.13
## @mastra/tanstack-start@0.2.41-alpha.13
## @mastra/voice-google-gemini-live@0.14.19-alpha.2
## @mastra/voice-openai-realtime@0.14.9-alpha.3
## @mastra/voice-xai-realtime@0.2.18-alpha.2
## @mastra/inngest@1.11.2-alpha.9
## @mastra/temporal@0.6.0-alpha.13
## create-mastra@1.39.0-alpha.15
## @internal/playground@1.39.0-alpha.15
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Description
Lets MCP clients such as Claude Code sign in to the built-in `/api/mcp`
endpoint with OAuth instead of a pasted token. The endpoint tells
clients where to sign in (RFC 9728 protected-resource metadata) and can
reject tokens issued for a different API (audience check).
```ts
new Mastra({
server: {
auth: new MastraJwtAuth({
jwksUri: 'https://auth.example.com/.well-known/jwks.json',
issuer: 'https://auth.example.com/',
}),
mcp: { oauth: { resource: 'https://my-app.example.com/api/mcp' } },
},
});
```
### Behavior changes
**OAuth discovery for `/api/mcp`** (`@mastra/server`, every server
adapter including NestJS)
- When `server.auth` is set and the built-in MCP server is on, a `401`
from `/api/mcp` carries `WWW-Authenticate: Bearer
resource_metadata="…"`. `error="invalid_token"` is added only when a
token was sent (RFC 6750 §3).
- Metadata is served publicly at
`/.well-known/oauth-protected-resource/api/mcp` and
`/.well-known/oauth-protected-resource`, with `Cache-Control: no-store`.
- The document lists `resource`, `authorization_servers`, optional
`scopes_supported`, and `bearer_methods_supported: ['header']`. Without
`oauth.resource`, `resource` is derived from the request origin.
- The challenge, metadata routes and audience check apply only to
`/api/mcp`. Other routes are unaffected.
**Audience check** (`server.mcp.oauth.resource`)
- When set, the token audience must include this exact value, or the
request gets 401.
- An invalid value (non-URL, or a non-loopback `http://` URL) turns
discovery off and logs an error, but the audience check still runs
against it. Requests fail closed until the value is fixed.
- A provider that can't check audience (no `verifyAudience`, for example
`SimpleAuth` API keys) is accepted by default. The server logs a startup
warning on adapters built on `MastraServer`, not on NestJS.
- `requireAudience: true` (opt-in, only valid together with `resource`)
rejects those requests on `/api/mcp` with 401 `invalid_token`. Inside
`CompositeAuth`, only requests accepted by such providers are rejected.
Without `resource`, nothing changes.
**Config and provider hooks** (`@mastra/core`)
- New `server.mcp.oauth` config: `resource`, `requireAudience`,
`authorizationServers`, `scopesSupported`.
- Two new optional auth-provider methods:
- `getOAuthMetadata()` advertises the provider's authorization server.
- `verifyAudience()` checks the token audience.
- `CompositeAuth` combines the authorization servers of its providers.
It checks the audience with the provider that accepted the token, and
rejects when that provider can't be determined. The new
`getAuthenticatedProvider(user)` returns that provider.
**Providers**
| Provider | Advertises its authorization server | Checks audience
against `oauth.resource` |
|---|---|---|
| `MastraJwtAuth` | Yes, its `issuer` | Yes |
| Auth0 | Yes, the tenant | Yes |
| Clerk | Yes, the Frontend API | No |
| Okta | Yes, the issuer | No: Okta already enforces its own `audience`
(`OKTA_AUDIENCE`) |
| Supabase | Yes, `<url>/auth/v1` (requires Supabase's OAuth 2.1 server)
| No |
`MastraJwtAuth` gains `jwksUri` and `issuer` options
(`JWT_AUTH_JWKS_URI`, `JWT_AUTH_ISSUER`), so it can verify tokens signed
by an identity provider. JWKS keys are restricted to their key type, so
HMAC tokens forged with the public key are rejected.
**JWT subject as user id** (`@mastra/auth`, Auth0, Clerk)
- When a token has no `id` claim, the user's `id` is now set to `sub`.
Existing `id` claims are kept.
- Standard OIDC access tokens only carry `sub`. Before this change, RBAC
never loaded roles for these users, so every protected route returned
`403 Missing required permission`.
- Unless `mapUserToResourceId` is set, this also scopes data for these
users:
- **Owned records** (stored agents, skills, workspaces and other owned
records): each user sees their own records plus public ones. Admin
permissions keep the full list.
- **Tool-provider connections:** per-author connections move from the
shared `default` owner to the user's `sub`. Existing connections need
reconnecting, or set `mapUserToResourceId: () => 'default'` to keep the
old shared behavior.
- **Feedback:** recorded with `sub` as the user id.
- The changeset describes all of these effects.
**Test suite** (`@mastra/server-adapters-test-suite`)
- New `createBuiltinMCPOAuthTestSuite`.
- The package now has `@mastra/auth` and `jose` as peer dependencies.
Stacked on #29929.
## Test plan
- `packages/server`: `src/server/mcp/oauth.test.ts` and
`oauth-without-mcp.test.ts`. They cover metadata, the challenge format,
resource validation, failing closed on an invalid `resource`, and
discovery working without `@mastra/mcp` installed.
- `packages/auth` `jwt.test.ts`:
- JWKS and issuer validation
- string and array `aud`
- an algorithm-confusion token that is HS256-signed with the real RSA
public key PEM and must be rejected
- `sub` used as `id`
- `packages/core` `composite-auth.test.ts`: per-provider audience
delegation, rejection when the authenticating provider is unknown, and
`getAuthenticatedProvider`.
- `auth/auth0`, `auth/clerk`, `auth/okta`, `auth/supabase` unit tests.
- `createBuiltinMCPOAuthTestSuite` on Hono, Express, Fastify, Koa and
Elysia, plus the NestJS equivalent. It checks:
- the challenge, and fetching the advertised metadata URL
- audience accept and reject, including for an invalid `resource`
- `requireAudience`:
- `SimpleAuth` + `resource`: 200 by default, 401 in strict mode
- a JWT with a matching audience: 200 in strict mode
- a mixed `CompositeAuth`: only the API key is rejected
- RBAC with a token that carries only `sub`
- that a `sub`-only user can't list another user's private stored agent
- `tsc --noEmit` and `oxlint` on the touched packages, plus docs `pnpm
check` and Vale.
- Manual run end to end with Claude Code against a local identity
provider: discovery, client registration, PKCE login, and two users with
different roles.
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
Dynamic agent config callbacks now get the authenticated end user as an
optional `user` argument, so you can personalize an agent without
digging auth keys out of `requestContext` yourself. It works in any
`DynamicArgument` callback: instructions, model, tools, memory,
workspace, processors, scorers, and so on.
```ts
import { Agent } from '@mastra/core/agent';
const supportAgent = new Agent({
id: 'support-agent',
instructions: ({ user }) =>
user ? `You are helping ${user.name ?? user.id}.` : 'You are a helpful assistant.',
model: ({ user }) => (user?.role === 'admin' ? 'openai/gpt-5' : 'openai/gpt-5-mini'),
tools: ({ user }) => (user ? { accountTool, ...(user.role === 'admin' ? { adminTool } : {}) } : {}),
memory: ({ user }) => (user ? userMemory : undefined),
});
```
`user` always has the same `MastraUser` shape, no matter which auth
provider you use, and it's `undefined` for unauthenticated requests:
```ts
import type { MastraUser } from '@mastra/core/types';
// { id: string; name?: string; email?: string; avatarUrl?: string; role?: string }
```
The server auth middleware builds it through a new overridable
`toMastraUser()` on `MastraAuthProvider`. The default handles common
shapes (`id`/`sub`/`userId`, `name`, `email`, `avatarUrl`/`picture`,
`role`), and JWT, Cloud, Supabase, Neon and Better Auth ship overrides
for their user objects. Custom providers can map their own shape:
```ts
import { MastraAuthProvider } from '@mastra/core/server';
import type { MastraUser } from '@mastra/core/types';
class MyAuth extends MastraAuthProvider<MyUser> {
async authenticateToken(token: string) { /* ... */ }
async authorizeUser(user: MyUser) { return true; }
toMastraUser(user: MyUser): MastraUser {
return { id: user.accountId, name: user.profile.displayName, role: user.permissions.primaryRole };
}
}
```
Inline auth configs can pass `toMastraUser` too. If the provider user
has no role and an RBAC provider is configured, the primary RBAC role
fills it in, so `user.role` also works with WorkOS, Okta, Google and
Neon. The raw provider user is still available when you need
provider-specific fields, and the new context key is reserved, so
clients can't spoof it through the request body:
```ts
instructions: ({ requestContext }) => {
const rawUser = requestContext.get('mastra__user'); // provider-specific object, unchanged
// ...
},
```
Dynamic `vectorStore` resolvers on RAG tools get `user` as well:
```ts
createVectorQueryTool({
indexName: 'docs',
model: embedder,
vectorStore: ({ user }) => (user ? tenantStores.get(user.id)! : sharedStore),
});
```
Inside core, every place that invoked a `DynamicArgument` callback
inline now goes through a single `resolveDynamicArgument` helper, which
reads the user from `requestContext` at call time. This is non-breaking:
callbacks get an extra optional field, providers get a method with a
working default. Requests served through an `MCPServer` don't get `user`
yet, since MCP builds its own request context; that's documented.
Tested with unit tests for the helper, normalization and each provider
override, middleware tests (inline config, provider role, RBAC role,
CompositeAuth ordering, unauthenticated), regression tests for the
migrated call sites, and an end-to-end test where an agent behind a fake
auth provider gets personalized instructions. Core, server, rag and the
touched auth packages typecheck clean, and their suites pass.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
When a signed-in user makes a request, configuration callbacks can now
use a standard set of details about that user. When a workflow resumes,
it uses the new request’s user details instead of restoring them from
the earlier run.
## Summary
- Added optional `user` data to `DynamicArgument` callbacks and RAG
vector-store resolvers. Callbacks can also use `getRequestUser()` to
read the normalized user from request context.
- Added the `MastraUser` type and `toMastraUser()` normalization hooks
for auth providers and inline auth configs. The server stores the
normalized user in a reserved request-context key and uses the primary
RBAC role when the user has no role.
- Updated core dynamic configuration paths to use the shared resolver.
Added user support to agent scopes and migrated A2A memory resolution.
- Added `withoutLiveRequestKeys()` to remove live authentication and
authorization data from saved context during workflow resume, restart,
and time travel. Saved non-authentication context, such as tenant data,
remains available.
- Added documentation and changesets. Raised relevant `@mastra/core`
peer dependency minimums to 1.81.0. MCPServer requests do not receive
the normalized `user`.
## Validation
The author reports passing typechecks and test suites across core,
server, RAG, and several auth packages. The author also reports three
failing Inngest tests and earlier failures in evented workflow and
scheduler tests, which reportedly fail the same way on comparison
sources. These results are author-reported and have not been
independently verified.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
Moves shared auth interfaces, providers, sessions, and EE auth helpers
into @internal/auth so auth provider packages no longer depend on
@mastra/core. The existing @mastra/core auth imports still work through
re-export stubs.
Before:
```ts
import { MastraAuthProvider } from '@mastra/core/server';
```
After, internal auth providers use:
```ts
import { MastraAuthProvider } from '@internal/auth/provider';
```
Verified with focused auth builds, lint, typecheck, and tests.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR moves the shared “auth code” (providers, sessions, and
enterprise features) out of `@mastra/core` into a new `@internal/auth`
package so all auth providers can reuse the same implementation.
`@mastra/core` keeps re-export stubs for compatibility, and new
lint/build rules help ensure providers stop importing from
`@mastra/core` directly.
## What changed
- Extracted shared auth internals into `@internal/auth`:
- Auth provider base classes and shared options (`MastraAuthProvider`,
`CompositeAuth`, `SimpleAuth`)
- Session types/providers (`Session`, `MemorySessionProvider`,
`CookieSessionProvider`)
- SSO/credentials/user auth types
- Enterprise Edition auth helpers:
- License validation + caching
- Telemetry bridge + EE capability detection
- RBAC/ACL/FGA interfaces and utilities (including `StaticRBACProvider`,
`FGADeniedError`, and `buildCapabilities`)
- Updated auth provider packages to import shared interfaces/helpers
from `@internal/auth` instead of `@mastra/core`.
- Added `no-restricted-imports` ESLint rules across auth packages to
prevent importing `@mastra/core` (including subpaths), with guidance to
use `@internal/auth`.
- Updated manifests and build configs so auth packages depend on
`@internal/auth` and generate types from the new entrypoints (narrowing
`generateTypes` scope to `@internal/auth`).
- Added new internal package entrypoints:
- `@internal/auth`
- `@internal/auth/provider`
- `@internal/auth/session`
- `@internal/auth/ee`
- `@internal/auth/ee/capabilities`
- Kept backward compatibility by converting many `@mastra/core` auth
exports into re-export stubs that delegate to `@internal/auth`.
## Notable internal auth additions
- New provider system:
- `MastraAuthProvider`
- `CompositeAuth`
- `SimpleAuth`
- New session providers:
- `MemorySessionProvider`
- `CookieSessionProvider`
- New EE helpers:
- License validation client and helpers
- Telemetry bridge
- RBAC/ACL/FGA interfaces and utilities
- Default roles + permission matching
- `buildCapabilities` and `FGADeniedError`
## Follow-up: narrower EE symbol exposure
- Updated core re-export entrypoints to reduce unintended EE symbol
leakage from broad `@internal/auth/ee` re-exports (using the dedicated
`@internal/auth/ee/capabilities` entrypoint and more targeted
FGA-related re-exports).
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Mastra Code (openai/gpt-5.5) <noreply@mastra.ai>
## Description
<!-- Required: Provide a brief description of the changes in this PR.
-->
## Related issue(s)
<!-- Required: Link to the issue(s) this PR addresses, e.g. with: Fixes
#123. PRs without linked issues may be closed. -->
## Type of change
- [ ] 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
- [ ] I have linked the related issue(s) in the description above
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR upgrades the Turbo monorepo build tool from version 2.9.6 to
2.9.12 and updates all configuration files across the entire codebase to
use the newer schema version that corresponds to this updated tool
version. Think of it like updating a recipe book to the latest version
and making sure all your cookbook references point to the new edition.
## Changes Summary
### Turbo Version Upgrade
- Updated root `package.json` `devDependencies`: `turbo` upgraded from
`^2.9.6` to `^2.9.12`
### Turbo Configuration Schema Updates
Updated the `$schema` field in 73 `turbo.json` configuration files
throughout the repository from the legacy
`https://turbo.build/schema.json` to the newer
`https://v2-9-16.turborepo.dev/schema.json`:
**Auth modules** (9 files): auth0, better-auth, clerk, cloud, firebase,
okta, studio, supabase, workos
**Client SDKs** (3 files): ai-sdk, client-js, react
**Deployers** (2 files): cloud, vercel
**Integrations** (3 files): brightdata, opencode, perplexity, tavily
**Observability** (11 files): arize, braintrust, datadog, laminar,
langfuse, langsmith, mastra, otel-bridge, otel-exporter, posthog, sentry
**Package modules** (19 files): _external-types, _internal-core,
agent-builder, auth, cli, codemod, core, create-mastra, deployer, evals,
fastembed, loggers, mcp, mcp-docs-server, mcp-registry-registry, memory,
playground, rag, schema-compat, server
**Data stores** (21 files): astra, chroma, clickhouse, cloudflare,
cloudflare-d1, convex, couchbase, duckdb, dynamodb, elasticsearch,
lance, libsql, mongodb, mssql, mysql, opensearch, pg, pinecone, qdrant,
redis, s3vectors, spanner, turbopuffer, upstash, vectorize
**Root configuration**: turbo.json
All other configuration content (extends, tasks, inputs/outputs) remains
unchanged across all files.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Summary
- Make `generateTypes` always validate generated declaration imports
against runtime dependencies, removing the opt-in
`validateRuntimeImports` option from all package tsup configs.
- Fix bundled declaration handling so API Extractor sees `.d.ts`
references instead of copied `.js` export targets.
- Align `@internal/external-types` bundled packages and metadata so its
generated rollup passes API Extractor.
## Test plan
- `node --check packages/_types-builder/src/index.js && node --check
packages/_types-builder/src/replace-types.js`
- `pnpm --filter @internal/external-types build:lib`
- `pnpm --filter @internal/external-types build`
- `pnpm --filter @internal/external-types lint`
- `pnpm --filter @mastra/fastembed build`
- `git diff --check`
## Notes
- `pnpm --filter @internal/external-types test` was not run because the
package has no matching test files.
- CodeRabbit CLI was available, but `coderabbit review --type
uncommitted --plain --no-color` timed out after 180s before returning
findings.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR makes TypeScript type validation **always happen** when building
packages, instead of being something teams could skip. It's like having
a mandatory safety check that ensures all the type information a package
exports only references dependencies it actually has—preventing broken
imports and confusing errors for users of the package.
## Summary
The PR enforces mandatory validation of generated TypeScript
declarations (`.d.ts` files) against runtime dependencies by removing
the optional `validateRuntimeImports` flag. All packages now always
validate their generated types.
## Key Changes
### Declaration Validation System
- **`packages/_types-builder/src/index.js`** (+116 lines) – Implements
`validateDeclarationRuntimeImports()` that scans generated `.d.ts` files
and rejects any import/export statements referencing packages not in the
package's `dependencies`, `peerDependencies`, `optionalDependencies`, or
bundled packages. Adds regex-based import specifier parsing, Node
built-in module detection, and error consolidation. Validates that all
type declarations only reference declared dependencies.
- **`packages/_types-builder/src/replace-types.js`** (+207 lines) –
Replaced streaming substring search with ts-morph-based declaration
rewriting. Now parses declarations to collect module specifiers from
import/export statements and `import("...")` type expressions, resolves
bundled package declarations using `resolve.exports` with `@types/*`
fallback, and copies resolved declarations into `dist/_types/<pkg>` with
rewritten module specifiers instead of appending `.js` extensions.
### Build Configuration Updates
- **122 `tsup.config.ts` files** across all package types (auth,
deployers, integrations, observability, stores, voice, workflows,
workspaces, client-sdks) – Updated `onSuccess` hooks to call
`generateTypes(process.cwd(), new Set())` or
`generateTypes(process.cwd(), new Set([packages]))` with explicit
dependency/bundled package sets instead of relying on defaults. This
removes the implicit `validateRuntimeImports` opt-in pattern.
### Bundled Package Declaration Handling
- **`packages/_external-types/api-extractor.json`** – Expanded
`bundledPackages` array to include `@ai-sdk/provider-utils`,
`@ai-sdk/ui-utils`, `@standard-schema/spec`, `eventsource-parser`,
`json-schema`, and `@opentelemetry/api` alongside `ai`.
- **`packages/_external-types/tsup.config.ts`** – Explicitly lists
bundled packages in `generateTypes()` call for proper type generation
and validation.
- **`packages/_external-types/src/index.ts`** – Added `@public` JSDoc
tag to `ProviderDefinedTool`.
### Dependency Adjustments
- **Auth packages** – Added `@mastra/core` peer dependency (`>=1.0.0-0
<2.0.0-0` or `>=1.32.0-0 <2.0.0-0`); some added `hono` peer dependency
(`^4.0.0`).
- **`packages/deployer/package.json`** – Moved `@hono/node-server` and
`@mastra/hono` from `devDependencies` to `dependencies`.
- **`packages/fastembed/tsup.config.ts`** – Updated to include
`@internal/ai-sdk-v4`, `@internal/ai-sdk-v5`, `@internal/ai-v6` in type
generation.
- **`packages/core/tsup.config.ts`** – Expanded dependency allowlist to
include `@ai-sdk/*`, `eventsource-parser`, and internal packages.
- **`packages/mcp/tsup.config.ts`** – Updated to generate types for
`hono` and `hono-mcp-server-sse-transport`.
- **`packages/schema-compat/package.json`** – Moved
`@standard-schema/spec`, `ajv`, `@types/json-schema` from
`devDependencies` to `dependencies`.
- **`packages/server/package.json`** – Moved `@mastra/schema-compat`
from `devDependencies` to `dependencies`.
- **`packages/_external-types/package.json`** – Added dev dependencies
for `@ai-sdk/ui-utils`, `@opentelemetry/api`, `@standard-schema/spec`,
`eventsource-parser`, `json-schema`.
- **Store packages** – Several added `zod` peer dependency (`^3.25.0 ||
^4.0.0`).
- **Server adapter packages** – `nestjs` added `zod` peer dependency;
`hono` added `hono` peer dependency; `server-adapters/hono/package.json`
added explicit `hono: ^4.12.8` peer dependency.
- **`deployers/netlify/package.json`** – Added `rollup` dependency
(`^4.0.0`).
- **`voice/cloudflare/package.json`** – Moved
`@cloudflare/workers-types` from `devDependencies` to `dependencies`.
- **`client-sdks/react/package.json`** – Added `@ai-sdk/react` and
`@assistant-ui/react` peer dependencies.
- **`stores/cloudflare-d1/package.json`** – Added
`@cloudflare/workers-types` peer dependency.
- **`observability/mastra/package.json`** – Added `zod` peer dependency.
### Path Resolution Updates
- **`client-sdks/react/src/agent/hooks.ts`** – Changed from `@/lib/...`
aliases to relative `../lib/...` imports.
- **`client-sdks/react/src/mastra-react-provider.tsx`** – Changed from
`@/` alias to relative path for `mastra-client-context` imports.
### Type Validation in MCP
- **`packages/mcp/src/server/server.ts`** – Made
`tool.parameters.validate()` and `tool.outputSchema.validate()` calls
awaited to handle async validators.
### JSON Schema Adapter
-
**`packages/schema-compat/src/standard-schema/adapters/json-schema.ts`**
– Updated Ajv import from `ajv/dist/2020` to `ajv/dist/2020.js`.
<!-- review_stack_entry_start -->
[](https://app.coderabbit.ai/change-stack/mastra-ai/mastra/pull/16752?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack)
<!-- review_stack_entry_end -->
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Mastra Code (openai/gpt-5.5) <noreply@mastra.ai>
## Summary
This PR reorganizes the test infrastructure across the monorepo by
introducing namespaced Vitest projects, proper test classification, and
a dedicated e2e CI job.
### Vitest project namespacing
- Rename all vitest project names from generic `'unit'` to
`'unit:<package-path>'` (e.g. `'unit:packages/core'`,
`'unit:auth/auth0'`) across ~100 packages
- Enables targeted test filtering with `--project 'unit:*'` glob
patterns in CI and locally
- Update CI workflow to use `'unit:*'` and `'typecheck:*'` patterns
### Test classification
- **Store tests** → `e2e:stores/*` (require external services like
Postgres, Redis, etc.)
- **RAG tests** → `e2e:packages/rag` (require embeddings API)
- **Evals LLM scorer tests** → `e2e:packages/evals` (require LLM API
keys)
- **pubsub tests** → `e2e:pubsub/*` (require Google Cloud)
- Add `isolate: false` to unit test configs for faster execution
### Core test reorganization
Split `agent.test.ts` (~7.5k lines) into focused unit test modules:
- `callbacks.test.ts` — callback/hook behavior
- `input-processors.test.ts` — input processing logic
- `instructions.test.ts` — instruction/system prompt handling
- `memory-metadata.test.ts` — memory metadata tests
- `save-and-errors.test.ts` — save behavior and error handling
- `title-generation.test.ts` — title generation logic
Renamed integration tests to `*.e2e.test.ts` for clarity (e.g.
`azure.integration.test.ts` → `azure.e2e.test.ts`).
### CI changes
- Add dedicated `e2e-test` job in `vitest-changed.yml` with shard-based
matrix
- Normalize shard names (`/` → `-`) for GitHub artifact compatibility
- Wire e2e job into `merge-reports` dependency chain
### Test fixes
- `tsx` → `tsx@latest` in MCP spawn calls to fix version resolution
- Rewrite `deployers/cloud` mock patterns for test reliability
- Skip network-dependent `mcp-registry-registry` tests (apitracker,
mcprun)
- Fix codemod `typeParameters` compatibility check
- Add `cwd` to CLI execa call
### Test plan
- Verified `pnpm vitest run --project 'unit:*'` runs only unit tests
- Verified `pnpm vitest run --project 'e2e:*'` runs only e2e tests
- Verified all extracted agent test files pass independently
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Tests**
* Added comprehensive test suites for agent features including
callbacks, input processors, instructions, memory handling, and title
generation across v1 and v2 implementations
* Reorganized test infrastructure with dedicated end-to-end test
workflows separate from unit tests
* Enhanced test isolation and parallel execution with named test
projects
* **Chores**
* Restructured test configuration across all packages for improved
organization and execution
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Mastra Code <noreply@mastra.ai>