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 -->
## 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>
## Description
Bump minimum required Node.js version to 22.13.0
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [X] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] 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
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Chores**
* Raised minimum Node.js requirement to 22.13.0 across the entire
package suite (core, SDKs, templates, deployers, stores, voice,
observability, examples).
* Issued major version bumps for the Mastra package suite.
* Added manifest validation to enforce presence of Node engine
declarations and cleaned up package metadata.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<!-- Provide a brief description of the changes in this PR -->
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
#123 -->
## 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 made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Breaking Changes**
* Major version bumps across deployer and authentication provider
packages
* **New Features**
* Authentication configuration option renamed from `experimental_auth`
to `auth` across all authentication integrations (Auth0, Clerk,
Firebase, Supabase, WorkOS, JWT)
* **Documentation**
* Updated all guides and examples to reflect the new authentication
configuration naming convention
<!-- end of auto-generated comment: release notes by coderabbit.ai -->