> Opened by @DSchau
## What
- `docs/package.json`: adds `packageManager` with the same pnpm pin as
the root (`pnpm@11.21.0+sha512…`). Vercel, Corepack and editors read
this field to choose the installer, so the docs project now declares
pnpm itself instead of depending on Vercel config.
- `docs/vercel.json`: sets `installCommand: "pnpm install
--frozen-lockfile"`. This is the same command
`packages/playground/vercel-preview/vercel.json` already uses, and it
makes the deploy explicit.
## Why
#28417 changed six docs dependencies to `catalog:`: `react`,
`react-dom`, `lucide-react`, `oxfmt`, `tsx` and `vitest`. Only pnpm
(with `pnpm-workspace.yaml`) can resolve that protocol. The
`mastra-docs-1.x` Vercel deploy passed on `52db47cd` and has failed on
every main commit since `ce5d4731` (#28417). `docs/` has neither a
lockfile nor a `packageManager` field, so a Vercel project rooted at
`docs` has to guess the installer. This PR keeps the catalog change and
pins docs to pnpm.
## Proof
- A local `pnpm build` in `docs/` passes on main (exit 0, 975 llms.txt
files generated).
- `pnpm install --frozen-lockfile` with the new field: "Already up to
date" on pnpm 11.21.0, no warnings about the docs package.
- `docs/package.json` has 0 `catalog:` entries at `52db47cd` and 6 at
main.
## Unverified
- I couldn't read the Vercel build logs, so the exact install error
isn't confirmed. This PR's `mastra-docs-1.x` preview is the real test.
- For Vercel to honor the exact pnpm version in `packageManager`, the
project needs `ENABLE_EXPERIMENTAL_COREPACK=1`. Without it, Vercel uses
its bundled pnpm.
- If the Vercel Root Directory is `docs`, "Include files outside the
root directory" must stay enabled so pnpm can see the workspace root.
## Risk: low
Config only, scoped to the docs package. Two keys to revert.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
The docs site uses package versions that only pnpm understands. This
change tells Vercel to use pnpm when it installs the docs dependencies,
and pins the pnpm version.
## Changes
- Added the pnpm 11.21.0 package-manager pin to `docs/package.json`.
- Set `installCommand` to `pnpm install --frozen-lockfile` in
`docs/vercel.json` and in the generator that creates it. This keeps the
generated configuration aligned with its source.
The supplied information reports a local build and install, but does not
verify the Vercel preview. Vercel build logs and review finding counts
were not provided.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
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 -->
Addresses the react-hook-form, Immer, and brace-expansion
vulnerabilities reported by Aikido. This raises react-hook-form to a
safe minimum, pins affected Immer 11 releases to 11.1.9, and overrides
vulnerable brace-expansion resolutions in the standalone observability
examples.
The full workspace build passed with 181/181 tasks, the repository-wide
typecheck passed, and the changed Hono example builds successfully.
Frozen-lockfile and supply-chain policy checks pass for the root
workspace and both standalone examples.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR updates unsafe package versions and locks vulnerable
dependencies to safe versions. It also keeps the standalone
observability examples aligned with the workspace configuration.
## Changes
- Updates `react-hook-form` to `^7.81.0` in the docs and playground
packages.
- Pins affected Immer 11 versions to `11.1.9`.
- Pins vulnerable `brace-expansion` versions in the observability
examples.
- Moves pnpm overrides to the workspace configuration for the Hono
example.
- Removes obsolete local package overrides from the Hono example package
configuration.
## Validation
- Full workspace build passed with 181/181 tasks.
- Repository-wide typecheck passed.
- Changed Hono example build passed.
- Frozen-lockfile checks passed.
- Supply-chain policy checks passed for the root workspace and both
standalone examples.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
**─────── TLDR ───────**
> lucide-react moves into the workspace catalog, so the design system
and its four consumers stop resolving three different versions of the
same icon set.
Every package declared its own range — `^0.474.0`, `^0.522.0`, `^1.23.0`
— and `@mastra/playground-ui` published a peer range, `^0.474.0`, that
two of them already failed to satisfy. A caret on a `0.x` version pins
the minor, so that peer was fiction the moment playground moved to
`0.522`. One catalog entry now feeds four of the five; docs carries the
same version as a literal.
I went to `^1.37.0` rather than `^1.38.0` because the repo's
`minimumReleaseAge` policy rejects 1.38, published yesterday.
### Behavior changed
Factory sidebar, Activity
├─ **was** — `ChartNoAxesGantt`, a stand-in because 0.474
had no timeline glyph
└─ **now** — `Timeline`, which 1.x adds
a GitHub or Slack mark, anywhere in Studio or Factory
├─ **was** — lucide's monochrome outline in six places, the
design system's own mark everywhere else
└─ **now** — the design system's mark in all of them; Slack
renders in brand color
a decorative lucide icon, under a screen reader
├─ **was** — announced as an unnamed image
└─ **now** — hidden: 1.x sets `aria-hidden` on any icon
given no label, one aria snapshot updated for it
### Decisions
- **peer range widened to `>=0.474.0 <2.0.0-0` instead of tracking the
catalog** — consumers outside this repo should not be forced onto 1.x;
all 164 icons the design system imports exist in both lines, and the
ceiling is there because 1.0 proved this package drops exports at majors
- **six brand icons moved rather than pinned to 0.x** — 1.x removes
`Github` and `Slack` outright, and `GithubIcon` / `SlackIcon` were
already the convention at 21 other call sites
- **docs stays on a literal `^1.37.0`, not `catalog:`** — its Vercel
project installs with npm, which rejects the protocol; bump it alongside
the catalog
### Watch
> [!WARNING]
> `@mastra/react` carries lucide as a real dependency, so it publishes
`^1.37.0`. An app pinned to lucide `0.x` now <mark>resolves a second
copy</mark> — bundle cost only, tree-shaken per icon. Nothing leaks into
the published types: lucide appears in the built chunks and in zero
`.d.ts` files.
---
> ██████████████████ **lockfile** `+23 −38` — net −15
> ████████████████ **source** `+21 −17`
> ████████ **changeset** `+10`
> ██████ **manifests** `+7 −5`
> ██ **tests** `+2 −4` — one aria snapshot
Replaces the static workflow JPGs with Mermaid diagrams across the
suspend and resume, human-in-the-loop, and control flow pages. The
diagrams use the shared docs theme, include accessible titles and
descriptions, and remove the unused image assets. The pnpm workspace
policy marks Mermaid's transitive `@types/koa-compose` package as
non-building.
Closes#21771
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
The documentation now uses interactive Mermaid diagrams instead of
static workflow images. The diagrams support light and dark modes and
include accessibility information.
## Changes
- Replaced workflow JPG diagrams with Mermaid diagrams for:
- Suspend and resume
- Human-in-the-loop
- Sequential and parallel control flow
- Added shared Mermaid rendering with:
- Light and dark color palettes
- Semantic node and edge styles
- Responsive layout and overflow handling
- Error-boundary fallback
- Added accessible diagram titles and descriptions.
- Added Mermaid authoring guidance for documentation contributors.
- Added Mermaid support and dependencies to the Docusaurus site.
- Added Mermaid examples to the kitchen-sink page.
- Removed unused diagram image assets.
- Updated Docusaurus dependencies and workspace build configuration.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Updates Tailwind CSS and its CLI, PostCSS, and Vite integrations to
4.3.3 across Playground, the React client, docs, and MastraCode web.
This aligns the mixed 4.2.2/4.3.0 toolchain and makes the v4.3 scrollbar
utilities already used by MessageScroller available in the generated
Playground UI CSS. The local Tailwind guidance is updated too.
Validated with frozen installs, the Playground UI and full Playground
dependency-graph builds, the docs build, the MastraCode web build, and
the Playground UI typecheck. Confirmed the autoscroll thumb and track
utilities are emitted in dist/style.css.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This updates Tailwind and related tools to the same newer version across
the project. It fixes transparent scrollbars in the Playground and makes
newer styling utilities available.
## Changes
- Upgraded Tailwind CSS 4.3.3 and related CLI, PostCSS, and Vite
integrations across:
- Playground
- Playground UI
- React client
- Documentation
- MastraCode web
- Enabled v4.3 scrollbar utilities used by `MessageScroller`.
- Updated Tailwind v4 local guidance to reference the new version and
utilities.
- Added a patch changeset for the Playground UI scrollbar fix.
## Validation
- Completed frozen installs and builds for the Playground UI, dependency
graph, docs, and MastraCode web.
- Typechecked the Playground UI.
- Confirmed scrollbar utilities are emitted in `dist/style.css`.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->