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>
Enable `no-useless-concat` and `typescript/prefer-as-const` in the
shared Oxlint config. Simplify 15 string concatenations and use const
assertions for four readonly SDK specification versions. Existing
package filters stay as configured.
String contents and expression evaluation order are preserved, and the
SDK fields keep their readonly `v1`–`v4` literal types. A documented
exception keeps NUL-delimited fixture records separate so the next
record’s leading digit cannot become an octal escape.
261 focused tests pass. A fresh scan clears both rules across 14,747
files, and emitted-JavaScript and declaration comparisons preserve
values and public field types. [CI lint and formatting
pass](https://github.com/mastra-ai/mastra/actions/runs/39583377036/job/119166317139)
for `93eb6e19d5`. The full core typecheck also passes after refreshing
workspace dependency declarations.
This maintenance PR intentionally includes no changeset and requests no
package releases. The Changesets status check may therefore fail. The
follow-up commit removes only release metadata; source code and tests
are unchanged from the validated revision.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This PR enables two lint rules and updates existing code to follow them.
It keeps the same runtime behavior, string values, and SDK version
types.
## Changes
- Enables `no-useless-concat` and `typescript/prefer-as-const` in
`oxlint.config.ts`.
- Simplifies 15 unnecessary string concatenations.
- Adds const assertions for the readonly SDK specification versions `v1`
through `v4`.
- Documents the intentional NUL-delimited fixture concatenation in
`mastracode/factory/src/routes/fs.test.ts`.
- Preserves public APIs, emitted values, evaluation order, and literal
types.
## Validation
- 261 focused tests pass.
- A fresh scan clears both lint rules across 14,747 files.
- Emitted JavaScript and declaration comparisons preserve values and
public field types.
- Core typecheck passes after refreshing workspace dependency
declarations.
- CI lint and formatting checks pass.
No changeset or package release is included because this is a
maintenance change.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
node-forge 1.4.0 is the newest release and is affected by CVE-2026-85393
(RSA PKCS#1 v1.5 signature forgery). There is no patched version, so the
only fix is to stop depending on it. This clears 3 open Vanta findings
(2 on the mastra-ai/mastra asset, 1 from Aikido).
It came in four ways:
- Root and `docs` package.json listed `node-forge` directly. These were
old Dependabot floors from #11359 and #14754. Nothing imports it, so
they're removed.
- `firebase-admin` 13 depended on it. v14 doesn't, but v14 also removed
the namespaced `admin.*` API, so `@mastra/auth-firebase` now uses
`firebase-admin/app` and `firebase-admin/auth`. It requires Node >= 22,
which the package already does.
- `@okta/okta-sdk-nodejs` -> `node-jose` -> `node-forge`. The latest
Okta SDK still has this chain. `MastraRBACOkta` only used the SDK for
`userApi.listUserGroups`, so it now calls `GET /api/v1/users/:id/groups`
with `fetch` and the same `SSWS` token header that
`MastraAuthOkta.getUser` already uses. It follows `Link: rel="next"`
pagination, but only to the configured org's origin, so the token never
goes anywhere else.
After this PR, `node-forge`, `node-jose` and `@okta/okta-sdk-nodejs` are
gone from `pnpm-lock.yaml`.
Testing: auth-okta and auth-firebase unit tests pass locally (I added
tests for pagination, the cross-origin guard, error retry and the ADC
fallback), and both packages build and typecheck.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This change removes packages that pull in `node-forge`, which the PR
reports has no patched release for the cited security issue. It keeps
Firebase authentication working with the newer Firebase Admin package
and fetches Okta groups directly from Okta.
## Changes
- Upgraded `firebase-admin` to `^14.5.0` and switched
`@mastra/auth-firebase` to modular Firebase Admin APIs. The provider
uses application-default credentials when no service account is
configured.
- Removed `@okta/okta-sdk-nodejs` from `@mastra/auth-okta`.
`MastraRBACOkta` now fetches group pages from Okta’s REST API and
follows pagination links only when they match the configured
organization’s origin.
- Removed direct `node-forge` dependencies from the root and docs
manifests. The supplied dependency search found no references to
`node-forge`, `node-jose`, or `@okta/okta-sdk-nodejs` in the lockfile.
- Added changesets for `@mastra/auth-firebase` and `@mastra/auth-okta`.
## Tests
The PR objectives report that auth-okta and auth-firebase unit tests
passed locally, and that both packages built and typechecked. These
results were not independently verified here.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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 -->
Moves Hono and hono-openapi out of @mastra/core runtime dependencies
while keeping their public types bundled in core declarations.
This should avoid duplicate Hono type instances for consumers without
requiring them to install Hono directly.
Before:
```ts
// Installing @mastra/core also installed Hono at runtime.
```
After:
```ts
// @mastra/core still exposes the same route and middleware types,
// but Hono is no longer installed as a runtime dependency.
```
Fixes#17405
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR stops bundling the Hono web framework inside `@mastra/core` and
related packages so projects only use one Hono installation provided by
the app, avoiding TypeScript type conflicts; `@mastra/core` still
exposes Hono-shaped types so existing code keeps working.
## Overview
- Moves Hono from runtime dependencies to dev/peer/dev-only entries so
`@mastra/core` no longer installs Hono at runtime but still includes
Hono types in generated declarations.
- Adds framework-agnostic request abstractions and helpers so auth
providers and server code accept both native Web Request and Hono-shaped
requests without requiring Hono at runtime.
- Reworks MCP and server modules to avoid leaking Hono runtime types
(e.g., Context) across package boundaries while preserving
Hono-compatible public types.
- Cleans up auth package manifests and implementations to remove runtime
Hono dependency and adopt the shared MastraAuthRequest surface.
## Key changes
- package metadata
- packages/core/package.json: removed hono and hono-openapi from runtime
deps; moved them to development/type-generation usage.
- Several auth packages (better-auth, cloud, okta, studio, workos):
removed hono from deps/devDeps/peerDeps where applicable.
- Build config
- packages/core/tsup.config.ts: added 'hono' and 'hono-openapi' to the
type-generation allowlist so their public types are emitted.
- New/shared request types & helpers
- packages/core/src/server/request-types.ts: introduces HonoRequestLike,
MastraAuthRequest (Request | HonoRequestLike), AuthenticateTokenFn,
AuthorizeUserFn, getRequestHeader, and getWebRequest.
- packages/core/src/server/index.ts: re-exports these types/helpers for
consumers.
- Auth API typing surface
- packages/core/src/server/auth.ts, types.ts, simple-auth.ts,
composite-auth.ts, and related tests: updated to use MastraAuthRequest
and the new callback types; tests updated to use real Web Request-based
mocks where appropriate.
- Auth provider implementations (auth/better-auth, auth/cloud,
auth/okta, auth/studio, auth/workos): updated to accept
MastraAuthRequest and use getRequestHeader/getWebRequest for
header/session access.
- MCP & server internals
- packages/core/src/mcp/types.ts: replaces Hono Context usage with a
HonoContextLike interface capturing only used shape.
- packages/mcp/src/server/server.ts and
packages/deployer/src/server/index.ts, plus server adapter code: added
local casting/adapters to keep runtime behavior while avoiding exported
Hono runtime types.
- packages/server/src/server/auth/helpers.ts and server-adapter: adapt
incoming requests to MastraAuthRequest and ensure middleware always
receives a normalized request.
- Types & tests
- Added type-test suite ensuring HonoRequest is assignable to the new
MastraAuthRequest-based provider types.
- Updated many tests to construct real Request objects and
MastraAuthRequest wrappers instead of Hono-specific mocks.
- Changeset
- .changeset/dull-papers-buy.md: documents removal of Hono runtime deps
and migration to framework-agnostic request types; triggers patch
releases.
## Impact
- Fixes `#17405` by preventing duplicate Hono instances and TypeScript
incompatibilities (e.g., conflicting Handler types).
- Consumers that use Hono should install it directly (peer dependency
semantics); consumers who do not use Hono are unaffected.
- Public type compatibility retained: Hono-shaped types remain available
through `@mastra/core`’s emitted declarations while runtime coupling to
Hono is removed.
Fixes `#17405`
<!-- review_stack_entry_start -->
[](https://app.coderabbit.ai/change-stack/mastra-ai/mastra/pull/17410?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>