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

548 commits

Author SHA1 Message Date
dane-ai-mastra[bot]
d60ba71be0 chore: version - exit prerelease mode 2026-11-12 21:12:29 +00: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
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
Arthur Fiorette
bd1fca831d
fix(deployer): build and serve file-based agents with CloudflareDeployer (#30003) 2026-11-10 20:32:18 -08:00
Dane - AI (Mastra)
c22107fce3
chore(deps): update dependency @ai-sdk/provider-utils@>=3.0.0 <3.0.38 to v3.0.45 (#29844) 2026-11-10 20:07:34 -08:00
YujohnNattrass
5c0f12c5a2
ci(mcp): fix MCP compatibility job on version-packages PRs (#29988)
Co-authored-by: YJ <yj@example.com>
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-10 19:55:49 -08:00
shreyas-mastra
8a301f6d66
chore(deps): force minimatch 11 and glob 14 for Vanta findings (#29916) 2026-11-10 12:57:20 -08:00
Arthur Fiorette
1ac251ba65
test(e2e): ensure CI fails when type checking fails (#29605)
## Description

Previously the e2e type-check job ran the type tests, ignored the result
and stayed green with 33 failures. `test.ts` now fails the job when any
run fails. It also runs plain `tsc`, because vitest skips type errors
outside test bodies.

For example, [E2E Type check in run
42058855421](https://github.com/mastra-ai/mastra/actions/runs/42058855421/job/127363177526)
passed with this in its log:

```
 Test Files  6 failed | 6 passed (12)
Type Errors  33 failed
```

Fixture tests that no longer matched the current types are updated. The
zero-argument `bail()` call is removed, since #12211 dropped that
overload on purpose. The `network()` tests now expect `undefined`
output, because `network()` ignores the agent's `defaultOptions`.

client-js `generateLegacy` typed `object` as `never` with `output` and
dropped `text` with `experimental_output`. It now infers both from the
schema:

```ts
const r = await agent.generateLegacy({ messages: 'hi', output: schema });
r.object; // before: never, now: inferred from schema
```

With #29581 merged, all type tests and both `tsc` runs pass.

## Related issue(s)

Fixes #29603
Fixes #29604

## 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


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

## ELI5

This PR makes the e2e type-check job report failures from all its
checks, including errors that test-focused checks can miss. It also
updates type tests to match current API types and fixes the result types
for `client-js` `generateLegacy()`.

## Changes

- The e2e type-check runner now runs two Vitest suites and two `tsc`
checks. It continues after a check fails and sets a failing exit status.
- The `generateLegacy()` overloads now retain schema types for `output`
and `experimental_output`. New type tests check the inferred `object`
and `text` types.
- Updated e2e type-test expectations for schemas, tools, workflows, and
client workflow start results.
- Updated `network()` tests to expect `undefined` when no structured
output is passed. This does not add inference from the agent’s
`TOutput`.
- Added a patch Changeset for `@mastra/client-js`.

## Validation

Completed CI, build, and test results: not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-10 08:29:06 -08:00
mastra-platform[bot]
4cd4c46e54
fix(core): release thread leases on shutdown (#29794)
## Summary

`Mastra.shutdown()` left behind the agent thread runs it was still
holding. Thread leases stayed held, and kept renewing with the
in-process pubsub, so another process couldn't use the thread until the
lease expired. Anyone following the run saw it fail with
`AgentThreadLeaseLostError`. This is the last open case of #27364; the
other four were fixed earlier.

Shutdown now hands those runs back once durable executions are
abandoned, while pubsub and storage are still open:

- **Parked runs** (waiting on a tool approval or suspension) are
announced with `run-suspended`, so they stay resumable.
- **Runs still executing** are aborted and get the rest of the drain
budget, at least 500 ms, to wind down, so they start no further steps.
Then the run ends with an unpersisted `run-completed`.
- The thread lease is released only after that event is published, and
only if the run has stopped. A run that hasn't stopped in time, such as
one whose tool ignores the abort, keeps its lease until it expires. A
tool's step counts as running until the tool body settles, not just
until the 250 ms abort grace hands control back to the loop.
- Every lease renewal this Mastra started stops.
- **Only this Mastra's runs are touched.** A run whose lease now belongs
to someone else is left alone. So is an evented run a worker executes
over a broker: it is only detached at shutdown, same as
`abandonDurableAgentExecutions`, and the worker keeps the lease.
- Abandoned durable runs now release their thread lease right away.
Recovery on the next boot no longer has to wait for the lease to lapse.

Late stream parts, suspended-run publishes and the run's own end are
skipped for runs shutdown already handed back, so nothing is published
twice.

Out of scope: whether followers of an abandoned durable run should wait
for recovery instead of ending.

Fixes #27364

## Test plan

- New `thread-shutdown-lease-release.test.ts`: two Mastra instances
share events and a lease backend that expires like Redis. Covers a
streaming run and a run parked on an approval, on every engine (normal,
durable, evented, fs). Checks that the lease is free right after
`shutdown()`, renewals and tool ticks stop, and the follower sees no
lost-lease error. All 8 fail without the fix.
- Updated the durable fence test: after shutdown, the thread lease no
longer marks the abandoned run live, so recovery works without mocking.
- `evented-execution.test.ts` still passes: when the API instance shuts
down, the run its worker executes keeps its thread lease.
- `src/agent/durable`, `src/agent/__tests__`, `src/mastra`: 6818 passed.
`durable-agent-crash-recovery.test.ts` hits a worker SIGABRT in this
sandbox, but that happens on main too.
- `tsc --noEmit`, oxlint and oxfmt are clean.
- Deployer `shutdown.test.ts` updated for the 6.5s core shutdown budget
(room for the handback).


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

## ELI5

When Mastra shuts down, it tells other processes whether each agent run
is paused or has ended. It stops renewing the run’s thread lease and
releases it when the run has stopped and the lease backend confirms
ownership, so another process can use the thread sooner. If a tool keeps
running after an abort, Mastra keeps the lease until it expires to avoid
handing the thread over too early.

## Changes

- Added shutdown handback for thread runs owned by the shutting-down
Mastra instance. Handback runs after durable executions are abandoned
and before pubsub teardown.
- Shutdown publishes `run-suspended` for parked runs and an unpersisted
`run-completed` event for other runs. It aborts executing runs and waits
for output, broadcasts, and running steps to settle within the grace
period.
- Shutdown releases a lease only if the run stopped and the lease
backend confirms that the instance still owns the lease. If a tool
ignores abort or the lease backend does not respond in time, shutdown
stops renewal and leaves the lease to expire.
- Runs executing elsewhere keep their lease. Shutdown suppresses later
stream parts and duplicate terminal events for runs it handles.
- Added shutdown tests for streaming, approval-parked, and partially
resumed runs across engines. A slow-tool test verifies that shutdown
does not release the lease while the abort-ignoring tool is still
running. Updated durable recovery and generated-server SIGTERM tests,
deployment guidance, the deployer shutdown budget, and the changeset.
- Diff size: 15 files changed, 873 lines added, 38 removed.

## Validation

Current-head test, build, and lint results: 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:39:52 -08:00
shreyas-mastra
bc9d8d482c
fix(deployer): don't allow CORS credentials for reflected origins by default (#29406)
With `server.auth` set and no `server.cors.origin`, the deployer server
reflected any request origin and also sent
`Access-Control-Allow-Credentials: true`. Any website could then make
cookie-authenticated requests to the server from a logged-in user's
browser and read the responses.

Now the origin is still reflected, but credentials are only on by
default when `server.cors.origin` lists allowed origins. An explicit
`server.cors.credentials` setting is respected either way. Without auth
nothing changes (`origin: '*'`, no credentials).

If you use cookie sessions from a browser app on another origin, set
`server.cors.origin` to that app's origin.

Updated the CORS tests for the three cases. Deployer server tests pass
(141), and `tsc` and lint are clean.


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

## ELI5

When authentication is on, the server can still reply to requests from
other websites. If it reflects a website’s origin, it no longer lets
that website use a visitor’s saved login credentials by default. List
allowed origins or set `server.cors.credentials` to allow credentials.

## Changes

- With `server.auth` set and `server.cors.origin` unset, the server
reflects the request origin but disables credentials by default.
- With an explicitly configured origin and auth enabled, credentials
remain enabled by default.
- An explicit `server.cors.credentials` setting takes precedence,
including when no origin is configured.
- Without auth, the default origin remains `'*'`.
- Updated CORS documentation, unit and end-to-end tests, and patch
changesets for `@mastra/deployer` and `@mastra/core`.

Test and lint results were not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-09 18:46:52 -05:00
Tyler Barnes
c87d691190
test(e2e): split the monorepo e2e suite into four files so they run in parallel (#29158)
## What

`e2e-tests/monorepo/monorepo.test.ts` held 85 tests that vitest ran on
one worker. That takes about 6.4 min in the E2E monorepo job. This PR
moves the auth, bundler and install suites into `monorepo-auth.test.ts`,
`monorepo-bundler.test.ts` and `monorepo-install.test.ts`. The shared
setup and helpers move to `helpers.ts`. vitest then runs the four files
on separate workers.

Each moved suite already built its own fixture (its own temp dir,
`setupMonorepo` and port), so none of them depended on the main file's
shared fixture. The test bodies are unchanged. `vitest.config.ts` adds
the three new files to `include`.

## Numbers

Measured in a 5-CPU container with 4 workers, the same as the CI runner,
on the same build and registry, two runs each:

| | Wall | Tests |
|---|---|---|
| before | 386 s / 381 s | 88 passed |
| after | 188 s / 188 s | 88 passed |

The CI Test step is about 396 s today, so the E2E monorepo job should
drop from about 7 min to about 4 min.

## Stacking

This is stacked on #29143 (the 3-way Affected UNIT split). Until that
lands, Affected UNIT is the long pole on core PRs, so this PR alone does
not shorten them. Retarget it to `main` after #29143 merges.

## Checks

- The test titles in the four files match the old single file one to
one: none dropped or duplicated.
- Prettier clean.


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

## ELI5

The monorepo end-to-end tests now run from separate files, so Vitest can
run them in parallel. The affected unit-test workflow can also split
large test lists across three jobs.

## Changes

- Moved authentication, bundler, and install tests out of
`monorepo.test.ts` into three test files.
- Added `helpers.ts` for shared fixtures, server and process cleanup,
lockfile parsing, and output checks.
- Added the three files to the monorepo Vitest configuration.
- Added configurable sharding to the affected unit-test workflow. It
uses three shards when at least 500 unit test files are affected and one
shard otherwise.

The diff changes 8 files, with 1,242 additions and 1,158 deletions. Test
and CI results are not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: remy-builder[bot] <324360501+remy-builder[bot]@users.noreply.github.com>
2026-11-09 13:22:17 -07:00
Arthur Fiorette
a836d09a43
fix(core, client-js, inngest): accept zod v3 schemas and newer ai v7 messages in public types (#29581)
## Description

zod v3 schemas work at runtime but some public types rejected them or
inferred `unknown`, and `UIMessage[]` from `ai@7.0.163` stopped
type-checking against core's vendored v7 types.

```ts
import { z } from 'zod/v3';
const schema = z.object({ answer: z.string() });

createStep(agent, { structuredOutput: { schema } }); // before: No overload matches this call
new Agent({ ...config, defaultOptions: { structuredOutput: { schema } } }); // before: TS2322
(await agent.generateLegacy('hi', { output: schema })).object; // before: unknown, now { answer: string }
await client.getAgent('a').generate('hi', { structuredOutput: { schema } }); // before: TS2590

import type { UIMessage } from 'ai'; // 7.0.163, has SteeringMessageUIPart
await agent.generate(uiMessages as UIMessage[]); // before: 'SteeringMessageUIPart' is not assignable
```

The zod v3 fixes point the user-facing option types at `PublicSchema` /
`PublicAgentExecutionOptions` (the runtime already converts with
`toStandardSchema`). `inferOutput` gets a zod v3 branch that reads
`_output` structurally, like `InferPublicSchema` in schema-compat, so a
v3 schema from a different zod install than core's is inferred too.
Client-js `StreamParamsBase` is built on `AgentExecutionOptionsBase`,
which avoids the TS2590.

For the v7 messages, `MessageInput` also accepts a v7 `UIMessage` whose
parts only need a string `type`. Core can't know the shape of part types
released after its vendored copy, so those parts are deliberately loose.
Inline object literals are still checked against the known part types,
because excess property checks rule out the loose member for them.
Mastra doesn't process the new part types yet.
`AIV6Adapter.fromUIMessage` paired parts with its v5 bridge output by
index, so a part the bridge drops (an unknown type, or an empty text
part) shifted every later part. It now drops those before pairing.

The PR also fixes two tests that failed CI on `main`: the stored board
runtime test still imported `factoryMemorySettingsUserId` after #29366
renamed it, and the redactor leak check matched `4111` inside a random
message UUID.

Type tests cover each case in the core and inngest type-test files, and
they fail with the fix reverted. The e2e client-js fixture imported
`zod/v3` and `zod/v4`, which don't resolve there, so its schemas were
`any`. This PR fixes those imports. The e2e type-check run still ignores
its exit code (`e2e-tests/type-check/test.ts:45`), which is left for a
separate PR.

## Related issue(s)

Fixes #29574
Fixes #29575

## 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
- [ ] 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
- [x] 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

This PR lets TypeScript accept Zod v3 schemas and newer AI SDK v7
messages in Mastra’s public APIs. It also fixes message-part matching so
ignored parts do not change how later parts are handled.

## Summary

- Updated agent and workflow option types to accept public schemas,
including Zod v3 schemas. Added Zod v3 output inference for
`generateLegacy`.
- Added forward-compatible input types for newer AI SDK v7 UI message
parts. Mastra accepts these messages, but does not yet process unknown
part types.
- Updated the AI v6 adapter to filter unsupported parts and empty text
parts before matching converted message parts.
- Updated client-js stream parameter types to avoid a complex TypeScript
union. Corrected Zod imports in a type-check fixture and added
regression type tests.
- Updated `getLastMessage` to use the last part only when it contains
nonempty string text.
- Added patch changesets for `@mastra/core`, `@mastra/client-js`, and
`@mastra/inngest`.

**Diff:** 19 files changed; 191 additions and 34 deletions.

**CI and test results:** not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-09 16:11:29 -03:00
Dane - AI (Mastra)
4bd4b7f48e
chore(deps): update better-auth monorepo to v1.7.18 (#29714)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-11-09 12:39:24 +01:00
Arthur Fiorette
d076f44bd7
fix(deployer): Windows backslash specifiers and deployer not stripped from build (#29578) 2026-11-05 14:14:02 -08:00
Arthur Fiorette
90e981b6e2
fix(deployer): stop option extraction from loading installed packages (#29558) 2026-11-05 11:37:02 -08:00
Arthur Fiorette
da7549b741
perf(deployer): skip the pino transport scan when it cannot match (#29454) 2026-11-05 14:02:07 -03:00
Dane - AI (Mastra)
bfe3af4ae1
chore(deps): update better-auth monorepo to v1.7.15 (#29497) 2026-11-04 17:36:58 -08:00
Dane - AI (Mastra)
9ce7e350ea
chore(deps): lock file maintenance (#29341)
Co-authored-by: wardpeet <ward@coding-tech.com>
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-11-04 15:03:55 +01:00
Arthur Fiorette
eaa3b5ce1e
fix(deployer): write chunks of extracted config options as .mjs (#29329) 2026-11-04 12:50:21 +01:00
Arthur Fiorette
52af646524
fix(deployer): only edit the root importer of the copied pnpm lockfile (#29330) 2026-11-04 12:49:42 +01:00
Arthur Fiorette
742b37dc32
fix(deployer): keep pnpm overrides scoped to the app working in the build output (#29350) 2026-11-03 17:48:21 -08:00
dane-ai-mastra[bot]
6e8dfcb83f chore: version - exit prerelease mode 2026-11-03 23:45:58 +00: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
c0fba5ea4d
fix(deployer): install the build output with the project's pnpm overrides (#29249) 2026-11-03 08:38:02 -08:00
Anurag Ojha
f62a2d6dc1
fix(observability): pin OTLP exporters to the OpenTelemetry SDK 2 line (#29265)
## Description

A Renovate bump moved the OTLP exporter packages in `observability/*` to
`0.300.0`, the OpenTelemetry SDK 3 line, while `sdk-trace-base`, `core`
and `resources` stayed on 2.x. The two lines need different
`@opentelemetry/api` versions, so npm hoists api 1.9.1 and the 0.300
exporters fail to load with `The requested module '@opentelemetry/api'
does not provide an export named 'SeverityNumber'`. pnpm in the monorepo
never hit it.

What users saw, all reproduced with fresh npm installs from the
registry:

- `import "@mastra/arize"` and `import "@mastra/arthur"` crash (the
linked issue).
- `@mastra/otel-exporter` 1.5.0 exports nothing. It loads its exporters
with a dynamic import, that import fails, and the catch logs "exporter
is not installed" and disables export. ESM and CommonJS, traces and
logs, every protocol, including the install commands in the docs. 1.4.10
exports fine.
- `import "@mastra/laminar"` crashes when installed next to
`@mastra/otel-exporter`.

Changes:

- Move the OTLP exporters back to `^0.223.0`, the last SDK 2 release, in
`@mastra/arize`, `@mastra/arthur`, `@mastra/laminar` and
`@mastra/otel-exporter`. No source change.
- Set `@opentelemetry/api` to `^1.9.0` in arize, arthur, laminar,
otel-exporter and otel-bridge. The same Renovate bump had raised it to
`^1.10.0`, and the SDK 2 packages need api below 1.10, so npm nested a
second api copy under each of our packages. A 1.10 copy cannot see the
tracer provider or the active span registered through the 1.9 copy
(checked with a real two-copy install). In the monorepo pnpm keeps
1.10.0, so only the lockfile specifiers change. Declaring it in arize
and arthur also keeps pnpm linking them to the same SDK instance as
otel-exporter.
- Widen otel-exporter's exporter `peerDependencies` from `^0.218.0`,
which on 0.x only matches 0.218.x, to `>=0.218.0 <0.300.0`, so they
agree with the optional dependencies.
- Add a Renovate rule that holds the six OTLP exporters below `0.300.0`
under `observability/*`. Renovate treats `0.22x -> 0.300` as a minor
update, so the major-approval gate did not stop it. A second rule keeps
the `@opentelemetry/api` ranges under `observability/*` as written and
updates only the lockfile, because the repo-wide `bump` strategy is what
raised them to `^1.10.0`. Remove both rules when `observability/*` moves
to SDK 3 together.
- Add the e2e suite `e2e-tests/npm-import`. It installs one template app
per install shape (arize and arthur, otel-exporter, laminar,
otel-bridge) with npm, not pnpm, imports and requires each package,
checks that npm installs one `@opentelemetry/api` copy, and sends a real
span through `OtelExporter` to a local server. It failed on the old
manifests with the errors above and passes on the fixed ones. It runs in
CI next to the sibling suites.

## Related issue(s)

Fixes #29175

## 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

Some packages used OpenTelemetry versions that did not work well
together after a fresh npm install. This PR aligns their version ranges
and adds checks for package loading, shared API installation, and trace
export.

## What changed

- Pins OTLP exporter dependencies to `^0.223.0` in `@mastra/arize`,
`@mastra/arthur`, `@mastra/laminar`, and `@mastra/otel-exporter`.
- Sets `@opentelemetry/api` to `^1.9.0` in the affected observability
packages, including `@mastra/otel-bridge`.
- Widens the six OTLP exporter peer dependency ranges in
`@mastra/otel-exporter` to `>=0.218.0 <0.300.0`.
- Adds Renovate rules to keep OTLP exporters below `0.300.0` and update
the API lockfile without changing its declared range.
- Adds an npm-import E2E suite that checks ESM imports, CommonJS
requires, a single installed API copy, and HTTP/protobuf trace export.
- Adds the suite to the E2E workflow and local registry publish
configuration, and adds patch changesets for the affected packages.

The supplied information does not establish test results.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-11-03 20:13:37 +05:30
Arthur Fiorette
501f010c0c
fix(deployer): stop packing workspace packages already bundled into the output (#29172)
## Description

In a monorepo, `mastra build` packs every workspace package the app
imports into `.mastra/output/workspace-module/` and installs it with its
whole dependency tree, even when the package is bundled into the output
and nothing imports it at runtime.

The packing seed in `Bundler._bundle` read from both
`analyzedBundleInfo.dependencies` (packages compiled into the bundle)
and `externalDependencies` (packages still imported at runtime). The
`dependencies` half came from #19808, as a fallback for workspace
subpaths that could leak into the output as bare imports. Since #24210
such a leak fails the build with
`DEPLOYER_BUNDLER_UNRESOLVED_WORKSPACE_IMPORT`, so the fallback only
adds tarballs. This PR seeds packing from `externalDependencies` only.
Transitive workspace dependencies of external workspace packages are
still collected from their `package.json`.

Before, in the monorepo E2E fixture (only `@inner/subpath-only` is in
`bundler.externals`):

```
Packaging batch 1/2: @inner/hello-world, @inner/inner-tools, @inner/lodash, @inner/native-binding-package, @inner/transitive-a
Packaging batch 2/2: @inner/transitive-b, @inner/transitive-c, @inner/subpath-only
```

After:

```
Packaging batch 1/1: @inner/subpath-only
```

Behavior change: code that loads a bundled workspace package at runtime
without a static import (`createRequire().resolve('@inner/x/...')`,
`node --import @inner/x`) used to work because the tarball happened to
be installed. Those packages now need to be listed in
`bundler.dynamicPackages`, the existing option for packages with no
static import, and the changeset says so. I checked that
`dynamicPackages: ['@repro/heavy']` packs and installs the workspace
package with this change, while `externals: ['@repro/heavy']` with no
import installs nothing (same as for third-party packages).

Verification:

- `@mastra/deployer` unit tests pass, and so does `tsc --noEmit`.
- Monorepo E2E suite locally: 85 of 88 pass. The 3 failures also happen
with the fix reverted and come from my local tooling: npm prints `npm
notice` on stderr during `mastra dev`, and pnpm 11.3 formats
`ERR_PNPM_IGNORED_BUILDS` differently.
- The new E2E assertion checks that `workspace-module/` only contains
`inner-subpath-only-1.0.0.tgz`. The changed-test gate confirmed it fails
against `main` and passes with the fix.

## Related issue(s)

Fixes #28303

## 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
- [ ] 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
- [x] I have addressed all Coderabbit comments on this PR
2026-11-02 09:27:27 -08:00
mastra-platform[bot]
1b40564c17
fix(deployer,cli): honor mastra dev --root for dev pre-bundle output (#29156) 2026-11-02 16:30:46 +01:00
Arthur Fiorette
49e59f251e
fix(core): accept voice providers from other packages in agent voice (#29074) 2026-10-31 11:12:15 -07:00
Arthur Fiorette
0b5c4e919e
fix(deployer): pin the installed package for subpath imports that ship their own package.json (#29076) 2026-10-31 11:10:48 -07:00
dane-ai-mastra[bot]
77076a1012 chore: version - exit prerelease mode 2026-10-30 23:02:25 +00:00
Arthur Fiorette
436b734df5
fix(deployer): apply bundler options when the project has file-based agents (#29054) 2026-10-30 15:30:42 -07:00
Dane - AI (Mastra)
8e0a56774d
chore(deps): update e2e-tests to ^5.9.3 (#29022)
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [typescript](https://www.typescriptlang.org/)
([source](https://redirect.github.com/microsoft/TypeScript)) |
devDependencies | patch | [`^5.9.2` →
`^5.9.3`](https://renovatebot.com/diffs/npm/typescript/5.9.2/5.9.3) |
| [typescript](https://www.typescriptlang.org/)
([source](https://redirect.github.com/microsoft/TypeScript)) |
dependencies | patch | [`^5.9.2` →
`^5.9.3`](https://renovatebot.com/diffs/npm/typescript/5.9.2/5.9.3) |

---

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

---

### Release Notes

<details>
<summary>microsoft/TypeScript (typescript)</summary>

###
[`v5.9.3`](https://redirect.github.com/microsoft/TypeScript/releases/tag/v5.9.3):
TypeScript 5.9.3

[Compare
Source](https://redirect.github.com/microsoft/TypeScript/compare/v5.9.2...v5.9.3)

Note: this tag was recreated to point at the correct commit. The npm
package contained the correct content.

For release notes, check out the [release
announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-9/)

- [fixed issues query for Typescript 5.9.0
(Beta)](https://redirect.github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.0%22+is%3Aclosed+).
- [fixed issues query for Typescript 5.9.1
(RC)](https://redirect.github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.1%22+is%3Aclosed+).
- *No specific changes for TypeScript 5.9.2 (Stable)*
- [fixed issues query for Typescript 5.9.3
(Stable)](https://redirect.github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.3%22+is%3Aclosed+).

Downloads are available on:

- [npm](https://www.npmjs.com/package/typescript)

</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.

🔕 **Ignore**: Close this PR and you won't be reminded about these
updates again.

---

- [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiI0NC4xOTguMiIsInVwZGF0ZWRJblZlciI6IjQ0LjE5OC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0aW9uIl19-->
2026-10-30 13:48:08 -07:00
shreyas-mastra
655b19993f
chore(security): Vanta 2026-10-30 - zod ^4.6.7, @hono/node-server 2.1.5 (direct bumps) (#28983)
## Vanta 2026-10-30 security fixes (consolidated)

Direct dependency bumps and lockfile updates only. **No
overrides/resolutions added or raised.** The earlier override-based
edits on this branch were reverted; those findings are deferred below.

| Package | From → To | Advisory | Where |
|---|---|---|---|
| zod | ^3.25.76 → ^4.6.7 | zod <4.6.6 (High; no fixed 3.x) |
`client-sdks/react` (dev), `deployers/cloudflare` (dev),
`server-adapters/nestjs` (dev), `packages/editor` (dev),
`packages/playground-ui` (dep), `packages/playground`,
`workflows/_test-utils`, `examples/{durable-agents,inngest}`,
`explorations/longmemeval`,
`observability/_examples/otel-bridge/agent-hub`, e2e fixtures/templates
(`experiment-worker/fixtures/*`, `deployers/template/cloudflare`,
`no-bundling/template`, agent-builder `minimal-mastra-project`) + root
`pnpm-lock.yaml` |
| @hono/node-server | 1.19.x / 2.1.1 → 2.1.5 | CVE-2026-118663 /
GHSA-rmxm-3fg6-px4f (Medium) | direct deps: `examples/agent-builder`,
`otel-bridge/hono-multi/service-{one,two,mastra}`,
`templates/template-customer-refund-agent/client-demo-ui`,
`templates/template-kyc-customer-onboarding`,
`templates/template-security-incident-triage` |

Peer ranges (`^3.25.0 || ^4.0.0`) are unchanged, so consumers are
unaffected. Changeset: patch for `@mastra/playground-ui` (runtime zod
dep).

Supersedes the zod parts of #28075 (that PR also raises a pnpm override
and rewrites the `zod-v3` compat aliases to v4, so it is left as-is for
maintainers).

### Deferred (needs override, upstream release, or is intentional)
- zod v3 compat aliases (`zod-v3` in `packages/core`,
`packages/schema-compat`, `e2e-tests/type-check/template`;
`e2e-tests/client-js/zod-v3`): intentional zod 3 test coverage; no fixed
3.x release. Needs a decision to drop/dismiss.
- zod 3.25.76 transitive via `@arcadeai/arcadejs`, `@mcp-ui/client`,
firecrawl, `agent-browser`, `zod-to-json-schema`, MCP SDK paths:
upstream pins; override-only.
- @hono/node-server 1.19.x transitive via `@modelcontextprotocol/sdk`
(root, `examples/agent`, `packages/mcp/integration-tests`), and npm
lockfiles of `scripts/gh-issue-triage` (existing override, left alone)
and the two templates: override-only.
- graphql-scalars, raw-body, jose (templates/scripts): override-only.
- @azure/msal-node <7.1.0: 6.0.1 via `@azure/identity@4.14.0` (fixed in
4.14.1, blocked by the 1-day `minimumReleaseAge`; lockfile refresh
tomorrow), 5.6.0 via `@microsoft/teams.apps` (no fixed release).
- @opentelemetry/core <2.8.0: via `@google-cloud/pubsub@5` (fix needs
pubsub 6 major).
- @ai-sdk/provider-utils 2.2.8 / ai 4.x: pinned vendored AI SDK v4 line;
no fixed release in that major.
- extract-zip, deepmerge: no patched version.


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

## ELI5

This PR updates Zod and `@hono/node-server` versions in selected
packages, examples, and templates to address security advisories. It
also updates playground form code to work with Zod 4.

## Changes

- Updates selected `zod` dependencies to `^4.6.7`.
- Updates selected `@hono/node-server` dependencies to `2.1.5`.
- Updates the playground form’s IP address and record validators for Zod
4.
- Maps a specific Zod validation error to the message `Required`.
- Adds a patch changeset for `@mastra/playground-ui`.

## Validation

Test results are not provided in the supplied change summary.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: shreyas-mastra <327047572+shreyas-mastra@users.noreply.github.com>
2026-10-30 15:30:35 -04:00
shreyas-mastra
e35d500c14
chore(security): Vanta 2026-10-29 - systeminformation 5.33.16, re2js 2.8.8, provider-utils 3.0.42 (nested lockfiles) (#28852) 2026-10-29 12:49:35 -07:00
Ward Peeters
6a18fc5094
refactor: move the bundler/deployer contract into @internal/deployer (#28428)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-10-29 16:25:04 +01:00
Dane - AI (Mastra)
9726ebcab4
chore(deps): update security updates [security] (#28238)
> [!NOTE]
> This PR body was truncated due to platform limits.

This PR contains the following updates:

| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
| [fast-uri@>=4.0.0
<4.1.5](https://redirect.github.com/fastify/fast-uri) |
pnpm-workspace.overrides | patch | [`4.2.1` →
`4.2.3`](https://renovatebot.com/diffs/npm/fast-uri@>=4.0.0
<4.1.5/4.2.1/4.2.3) | |
| [hono](https://hono.dev)
([source](https://redirect.github.com/honojs/hono)) | devDependencies |
patch | [`4.13.11` →
`4.13.12`](https://renovatebot.com/diffs/npm/hono/4.13.11/4.13.12) | |
|
[ip-address@<10.7.1](https://redirect.github.com/beaugunderson/ip-address)
| pnpm-workspace.overrides | patch | [`10.7.2` →
`10.7.4`](https://renovatebot.com/diffs/npm/ip-address@<10.7.1/10.7.2/10.7.4)
| |
| [nodemailer](https://nodemailer.com/)
([source](https://redirect.github.com/nodemailer/nodemailer)) |
dependencies | minor | [`^10.1.1` →
`^10.2.1`](https://renovatebot.com/diffs/npm/nodemailer/10.1.1/10.2.1) |
`10.3.0` |
| [qs](https://redirect.github.com/ljharb/qs) | pnpm-workspace.overrides
| patch | [`6.16.0` →
`6.16.1`](https://renovatebot.com/diffs/npm/qs/6.16.0/6.16.1) | |
| [qs@>=6.7.0 <6.16.0](https://redirect.github.com/ljharb/qs) |
pnpm-workspace.overrides | patch | [`6.16.0` →
`6.16.1`](https://renovatebot.com/diffs/npm/qs@>=6.7.0
<6.16.0/6.16.0/6.16.1) | |
|
[serialize-javascript@<7.0.5](https://redirect.github.com/yahoo/serialize-javascript)
| pnpm-workspace.overrides | minor | [`^7.0.5` →
`^7.1.4`](https://renovatebot.com/diffs/npm/serialize-javascript@<7.0.5/7.0.5/7.1.4)
| |
| [systeminformation@<5.32.0](https://systeminformation.io)
([source](https://redirect.github.com/sebhildebrandt/systeminformation))
| pnpm-workspace.overrides | patch | [`5.33.13` →
`5.33.16`](https://renovatebot.com/diffs/npm/systeminformation@<5.32.0/5.33.13/5.33.16)
| |
| [zod](https://zod.dev)
([source](https://redirect.github.com/colinhacks/zod)) | dependencies |
minor | [`^4.0.0` →
`^4.6.7`](https://renovatebot.com/diffs/npm/zod/4.0.0/4.6.7) | |

---

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

---

### fast-uri vulnerable to scheme injection via an unescaped
first-segment colon in suffix references
[CVE-2026-110725](https://nvd.nist.gov/vuln/detail/CVE-2026-110725) /
[GHSA-333x-w4r6-6crp](https://redirect.github.com/advisories/GHSA-333x-w4r6-6crp)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri`'s `serialize()`, `normalize()`, and `resolve()`, when called
with the non-default option `reference: 'suffix'` on a reference that
has no authority, emit a relative reference whose first path segment
contains a bare colon without escaping it. RFC 3986 section 3.3 requires
the first segment of a `path-noscheme` reference not to contain a colon,
precisely because a bare colon makes the string reparse as an absolute
URI with a scheme. `fast-uri`'s default serialization escapes that
colon, but the suffix path does not.

For example, `normalize('javascript:alert(1)', { reference: 'suffix' })`
returns `javascript:alert(1)`, which reparses as a live `javascript:`
scheme; `data:` and `vbscript:` behave the same.

Applications that serialize or normalize a relative reference with
`reference: 'suffix'` and then treat the result as a URI can turn inert
input into a live `javascript:`, `data:`, or `vbscript:` URL (a
cross-site scripting vector), and `equal()` can conflate a
scheme-bearing reference with a relative one. Exposure is limited to
applications that use the non-default `reference: 'suffix'` option.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Do not use the `reference: 'suffix'` option on untrusted input. If
suffix output is required, percent-encode a colon in the first path
segment of the result before treating it as a URI.

#### Severity
- CVSS Score: 3.7 / 10 (Low)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-333x-w4r6-6crp](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-333x-w4r6-6crp)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110725](https://nvd.nist.gov/vuln/detail/CVE-2026-110725)
-
[39e6493c13)
-
[a9b8d67353)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)
-
[https://github.com/advisories/GHSA-333x-w4r6-6crp](https://redirect.github.com/advisories/GHSA-333x-w4r6-6crp)

This data is provided by the [GitHub Advisory
Database](https://redirect.github.com/advisories/GHSA-333x-w4r6-6crp)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### fast-uri vulnerable to host confusion via unchecked WHATWG host
canonicalization
[CVE-2026-110180](https://nvd.nist.gov/vuln/detail/CVE-2026-110180) /
[GHSA-wjr9-j795-jxcr](https://redirect.github.com/advisories/GHSA-wjr9-j795-jxcr)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri` versions `>= 2.4.2, <= 2.4.7`, `>= 3.1.3, <= 3.1.8`, and `>=
4.0.1, <= 4.2.2` can silently rewrite the host of an HTTP-family URL
(`http`, `https`, `ws`, `wss`, or any scheme with `domainHost: true`).
For those schemes `canonicalizeHost()` passes the parsed host to the
WHATWG `URL` parser and adopts its `.hostname` without checking that the
parser read the whole input as a host. RFC 3986 permits `@` inside the
host group and the WHATWG parser strips TAB, LF, and CR, so the
authority `fast-uri` reports is rewritten by that second parser with no
`error` set: data before an `@` is dropped and whitespace is removed.

For example, `fast-uri` parses `http://a@b@evil.example/` to host
`evil.example` (dropping the `b` segment), and a host containing a raw
TAB, CR, or LF has those characters stripped. `equal()` then treats a
whitespace-smuggled host as the same as the clean one, and `resolve()`
rewrites the authority the same way.

Applications that use `fast-uri` to enforce host-based policy
(denylists, loopback filtering, redirect validation, outbound proxy
routing) on one representation, such as the raw input, see a policy/use
desync: the canonical host `fast-uri` returns differs from what was
checked, and traffic can be steered to an unintended destination.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Reject URIs whose authority contains more than one `@`, or contains TAB,
CR, or LF, before calling `fast-uri`. Alternatively, treat any non-empty
`parse(x).error` as fatal, and compare hosts only from the same
`parse()` result.

#### Severity
- CVSS Score: 4.8 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-wjr9-j795-jxcr](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-wjr9-j795-jxcr)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110180](https://nvd.nist.gov/vuln/detail/CVE-2026-110180)
-
[58c183d0b1)
-
[ddfc6a5112)
-
[f6d46dfeab)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)
-
[https://github.com/advisories/GHSA-wjr9-j795-jxcr](https://redirect.github.com/advisories/GHSA-wjr9-j795-jxcr)

This data is provided by the [GitHub Advisory
Database](https://redirect.github.com/advisories/GHSA-wjr9-j795-jxcr)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### fast-uri vulnerable to improper path equivalence in relative
reference normalization
[CVE-2026-110095](https://nvd.nist.gov/vuln/detail/CVE-2026-110095) /
[GHSA-xhq7-xmqj-769h](https://redirect.github.com/advisories/GHSA-xhq7-xmqj-769h)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri`'s `normalize()` and `serialize()` apply RFC 3986 dot-segment
removal (`remove_dot_segments`) to the path of a relative-path
reference. RFC 3986 section 5.2.4 defines that algorithm only for the
merged target path during resolution, not for the reference itself, so
applied to the reference it drops leading `..` segments and can turn a
document-relative reference into a root-relative one.

For example, `normalize('a/../b')` returns `/b` and `normalize('../x')`
returns `x`, so `resolve(base, normalize(ref))` points at a different
resource than `resolve(base, ref)`, and `equal()` treats distinct
references as the same.

Applications that normalize attacker-supplied or user-supplied relative
references and then resolve them, or use them as cache, deduplication,
or authorization keys, can have a reference escape its intended
directory and point at a different resource.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Do not normalize a relative reference before resolving it. Resolve it
against the absolute base first, then normalize the absolute result.

#### Severity
- CVSS Score: 3.7 / 10 (Low)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-xhq7-xmqj-769h](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-xhq7-xmqj-769h)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110095](https://nvd.nist.gov/vuln/detail/CVE-2026-110095)
-
[048bbd0a25)
-
[52774a5c35)
-
[7c19f8b97e)
-
[9eb8759a98)
-
[acc5c5d60c)
-
[b110a3571c)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)
-
[https://github.com/advisories/GHSA-xhq7-xmqj-769h](https://redirect.github.com/advisories/GHSA-xhq7-xmqj-769h)

This data is provided by the [GitHub Advisory
Database](https://redirect.github.com/advisories/GHSA-xhq7-xmqj-769h)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### fast-uri vulnerable to URI scheme spoofing via percent-encoded
scheme decoding
[CVE-2026-110306](https://nvd.nist.gov/vuln/detail/CVE-2026-110306) /
[GHSA-w74x-v6f9-j3xg](https://redirect.github.com/advisories/GHSA-w74x-v6f9-j3xg)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri` percent-decodes the scheme component with the legacy global
`unescape()` before validating it, so an input whose decoded scheme is a
valid but dangerous token is emitted as a live scheme. RFC 3986 section
3.1 does not allow percent-encoding in a scheme, so no RFC or WHATWG
parser treats such input as having that scheme, but `fast-uri` does.

For example, `normalize('%6Aavascript:alert(1)')` returns
`javascript:alert(1)`, `resolve('https://a.example/',
'%6Aavascript:alert(1)')` returns `javascript:alert(1)`, and
`parse('%6Aavascript:alert(1)').scheme` returns `javascript`. The
`%uXXXX` form (`%u006Aavascript:`) produces the same result, and
`equal('%68ttp://a/', 'http://a/')` returns `true`.

An application that screens dangerous schemes on the raw input and then
stores or renders `normalize(input)` or `resolve(base, input)` turns an
inert string into an executable `javascript:`, `data:`, or `vbscript:`
URL, a stored or reflected cross-site scripting vector in the consuming
application. `equal()` also treats an encoded and a plain scheme as the
same, which can bypass equality-based allowlists.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Reject input whose scheme part (before the first `:`, and before any
`/`, `?`, or `#`) contains `%`. Alternatively, check `parse(x).scheme`
against an allowlist after normalization and use that same parsed result
rather than the raw string.

#### Severity
- CVSS Score: 6.1 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-w74x-v6f9-j3xg](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-w74x-v6f9-j3xg)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110306](https://nvd.nist.gov/vuln/detail/CVE-2026-110306)
-
[39933a1f14)
-
[597f254c86)
-
[e60e716f41)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)
-
[https://github.com/advisories/GHSA-w74x-v6f9-j3xg](https://redirect.github.com/advisories/GHSA-w74x-v6f9-j3xg)

This data is provided by the [GitHub Advisory
Database](https://redirect.github.com/advisories/GHSA-w74x-v6f9-j3xg)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### fast-uri vulnerable to scheme injection via an unescaped
first-segment colon in suffix references
[CVE-2026-110725](https://nvd.nist.gov/vuln/detail/CVE-2026-110725) /
[GHSA-333x-w4r6-6crp](https://redirect.github.com/advisories/GHSA-333x-w4r6-6crp)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri`'s `serialize()`, `normalize()`, and `resolve()`, when called
with the non-default option `reference: 'suffix'` on a reference that
has no authority, emit a relative reference whose first path segment
contains a bare colon without escaping it. RFC 3986 section 3.3 requires
the first segment of a `path-noscheme` reference not to contain a colon,
precisely because a bare colon makes the string reparse as an absolute
URI with a scheme. `fast-uri`'s default serialization escapes that
colon, but the suffix path does not.

For example, `normalize('javascript:alert(1)', { reference: 'suffix' })`
returns `javascript:alert(1)`, which reparses as a live `javascript:`
scheme; `data:` and `vbscript:` behave the same.

Applications that serialize or normalize a relative reference with
`reference: 'suffix'` and then treat the result as a URI can turn inert
input into a live `javascript:`, `data:`, or `vbscript:` URL (a
cross-site scripting vector), and `equal()` can conflate a
scheme-bearing reference with a relative one. Exposure is limited to
applications that use the non-default `reference: 'suffix'` option.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Do not use the `reference: 'suffix'` option on untrusted input. If
suffix output is required, percent-encode a colon in the first path
segment of the result before treating it as a URI.

#### Severity
- CVSS Score: 3.7 / 10 (Low)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-333x-w4r6-6crp](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-333x-w4r6-6crp)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110725](https://nvd.nist.gov/vuln/detail/CVE-2026-110725)
-
[39e6493c13)
-
[a9b8d67353)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri](https://redirect.github.com/fastify/fast-uri)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-333x-w4r6-6crp) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### fast-uri vulnerable to URI scheme spoofing via percent-encoded
scheme decoding
[CVE-2026-110306](https://nvd.nist.gov/vuln/detail/CVE-2026-110306) /
[GHSA-w74x-v6f9-j3xg](https://redirect.github.com/advisories/GHSA-w74x-v6f9-j3xg)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri` percent-decodes the scheme component with the legacy global
`unescape()` before validating it, so an input whose decoded scheme is a
valid but dangerous token is emitted as a live scheme. RFC 3986 section
3.1 does not allow percent-encoding in a scheme, so no RFC or WHATWG
parser treats such input as having that scheme, but `fast-uri` does.

For example, `normalize('%6Aavascript:alert(1)')` returns
`javascript:alert(1)`, `resolve('https://a.example/',
'%6Aavascript:alert(1)')` returns `javascript:alert(1)`, and
`parse('%6Aavascript:alert(1)').scheme` returns `javascript`. The
`%uXXXX` form (`%u006Aavascript:`) produces the same result, and
`equal('%68ttp://a/', 'http://a/')` returns `true`.

An application that screens dangerous schemes on the raw input and then
stores or renders `normalize(input)` or `resolve(base, input)` turns an
inert string into an executable `javascript:`, `data:`, or `vbscript:`
URL, a stored or reflected cross-site scripting vector in the consuming
application. `equal()` also treats an encoded and a plain scheme as the
same, which can bypass equality-based allowlists.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Reject input whose scheme part (before the first `:`, and before any
`/`, `?`, or `#`) contains `%`. Alternatively, check `parse(x).scheme`
against an allowlist after normalization and use that same parsed result
rather than the raw string.

#### Severity
- CVSS Score: 6.1 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-w74x-v6f9-j3xg](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-w74x-v6f9-j3xg)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110306](https://nvd.nist.gov/vuln/detail/CVE-2026-110306)
-
[39933a1f14)
-
[597f254c86)
-
[e60e716f41)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri](https://redirect.github.com/fastify/fast-uri)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-w74x-v6f9-j3xg) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### fast-uri vulnerable to host confusion via unchecked WHATWG host
canonicalization
[CVE-2026-110180](https://nvd.nist.gov/vuln/detail/CVE-2026-110180) /
[GHSA-wjr9-j795-jxcr](https://redirect.github.com/advisories/GHSA-wjr9-j795-jxcr)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri` versions `>= 2.4.2, <= 2.4.7`, `>= 3.1.3, <= 3.1.8`, and `>=
4.0.1, <= 4.2.2` can silently rewrite the host of an HTTP-family URL
(`http`, `https`, `ws`, `wss`, or any scheme with `domainHost: true`).
For those schemes `canonicalizeHost()` passes the parsed host to the
WHATWG `URL` parser and adopts its `.hostname` without checking that the
parser read the whole input as a host. RFC 3986 permits `@` inside the
host group and the WHATWG parser strips TAB, LF, and CR, so the
authority `fast-uri` reports is rewritten by that second parser with no
`error` set: data before an `@` is dropped and whitespace is removed.

For example, `fast-uri` parses `http://a@b@evil.example/` to host
`evil.example` (dropping the `b` segment), and a host containing a raw
TAB, CR, or LF has those characters stripped. `equal()` then treats a
whitespace-smuggled host as the same as the clean one, and `resolve()`
rewrites the authority the same way.

Applications that use `fast-uri` to enforce host-based policy
(denylists, loopback filtering, redirect validation, outbound proxy
routing) on one representation, such as the raw input, see a policy/use
desync: the canonical host `fast-uri` returns differs from what was
checked, and traffic can be steered to an unintended destination.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Reject URIs whose authority contains more than one `@`, or contains TAB,
CR, or LF, before calling `fast-uri`. Alternatively, treat any non-empty
`parse(x).error` as fatal, and compare hosts only from the same
`parse()` result.

#### Severity
- CVSS Score: 4.8 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-wjr9-j795-jxcr](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-wjr9-j795-jxcr)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110180](https://nvd.nist.gov/vuln/detail/CVE-2026-110180)
-
[58c183d0b1)
-
[ddfc6a5112)
-
[f6d46dfeab)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri](https://redirect.github.com/fastify/fast-uri)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-wjr9-j795-jxcr) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### fast-uri vulnerable to improper path equivalence in relative
reference normalization
[CVE-2026-110095](https://nvd.nist.gov/vuln/detail/CVE-2026-110095) /
[GHSA-xhq7-xmqj-769h](https://redirect.github.com/advisories/GHSA-xhq7-xmqj-769h)

<details>
<summary>More information</summary>

#### Details
##### Impact

`fast-uri`'s `normalize()` and `serialize()` apply RFC 3986 dot-segment
removal (`remove_dot_segments`) to the path of a relative-path
reference. RFC 3986 section 5.2.4 defines that algorithm only for the
merged target path during resolution, not for the reference itself, so
applied to the reference it drops leading `..` segments and can turn a
document-relative reference into a root-relative one.

For example, `normalize('a/../b')` returns `/b` and `normalize('../x')`
returns `x`, so `resolve(base, normalize(ref))` points at a different
resource than `resolve(base, ref)`, and `equal()` treats distinct
references as the same.

Applications that normalize attacker-supplied or user-supplied relative
references and then resolve them, or use them as cache, deduplication,
or authorization keys, can have a reference escape its intended
directory and point at a different resource.

##### Patches

Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`.

##### Workarounds

Do not normalize a relative reference before resolving it. Resolve it
against the absolute base first, then normalize the absolute result.

#### Severity
- CVSS Score: 3.7 / 10 (Low)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`

#### References
-
[https://github.com/fastify/fast-uri/security/advisories/GHSA-xhq7-xmqj-769h](https://redirect.github.com/fastify/fast-uri/security/advisories/GHSA-xhq7-xmqj-769h)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-110095](https://nvd.nist.gov/vuln/detail/CVE-2026-110095)
-
[048bbd0a25)
-
[52774a5c35)
-
[7c19f8b97e)
-
[9eb8759a98)
-
[acc5c5d60c)
-
[b110a3571c)
-
[https://cna.openjsf.org/security-advisories.html](https://cna.openjsf.org/security-advisories.html)
-
[https://github.com/fastify/fast-uri](https://redirect.github.com/fastify/fast-uri)
-
[https://github.com/fastify/fast-uri/releases/tag/v2.4.8](https://redirect.github.com/fastify/fast-uri/releases/tag/v2.4.8)
-
[https://github.com/fastify/fast-uri/releases/tag/v3.1.9](https://redirect.github.com/fastify/fast-uri/releases/tag/v3.1.9)
-
[https://github.com/fastify/fast-uri/releases/tag/v4.2.3](https://redirect.github.com/fastify/fast-uri/releases/tag/v4.2.3)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-xhq7-xmqj-769h) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Hono: `serveStatic` decodes the request path a second time, leading
to bypass of middleware on static paths
[CVE-2026-109955](https://nvd.nist.gov/vuln/detail/CVE-2026-109955) /
[CVE-2026-111757](https://nvd.nist.gov/vuln/detail/CVE-2026-111757) /
[GHSA-5r4p-p66f-jhc7](https://redirect.github.com/advisories/GHSA-5r4p-p66f-jhc7)

<details>
<summary>More information</summary>

#### Details
##### Summary

`serveStatic` decodes the request path a second time after Hono has
already decoded it for routing. A crafted request can be routed as one
path and served as another, so middleware mounted on a static prefix
does not run for a file under that prefix.

##### Details

Hono decodes the request path once before routing. `serveStatic` decoded
it again before resolving the file. With a malformed percent-encoded
sequence, the first decode leaves part of the path encoded, the router
matches the encoded form, and the second decode resolves the real
directory. The file is still resolved inside the configured root; this
is not a traversal outside it.

##### Impact

An unauthenticated attacker may reach static files without the
middleware on their prefix running, for example an authentication check.
This affects applications that mount middleware on part of the directory
served by `serveStatic`. Applications that serve only public files are
not affected.

#### Severity
- CVSS Score: 5.3 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`

#### References
-
[https://github.com/honojs/hono/security/advisories/GHSA-5r4p-p66f-jhc7](https://redirect.github.com/honojs/hono/security/advisories/GHSA-5r4p-p66f-jhc7)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-111757](https://nvd.nist.gov/vuln/detail/CVE-2026-111757)
-
[8b05c774ef)
-
[https://github.com/honojs/hono](https://redirect.github.com/honojs/hono)
-
[https://github.com/honojs/hono/releases/tag/v4.13.11](https://redirect.github.com/honojs/hono/releases/tag/v4.13.11)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-5r4p-p66f-jhc7) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### ip-address: Address6 matches a zone identifier in quadratic time
ahead of its length limit, allowing a single long string to stall the
process
[CVE-2026-111997](https://nvd.nist.gov/vuln/detail/CVE-2026-111997) /
[GHSA-rxp7-6hxx-x8q5](https://redirect.github.com/advisories/GHSA-rxp7-6hxx-x8q5)

<details>
<summary>More information</summary>

#### Details
##### Summary

`new Address6()` and `Address6.isValid()` strip a zone identifier with
the pattern `/%.*$/` before they apply the 45-character length limit.
When the string holds many `%` characters followed by a line terminator,
the pattern is retried from every `%` and each attempt scans to the line
terminator before failing, so rejecting the string takes time
proportional to the square of its length. 10,000 `%` characters and a
newline take 41 ms, 40,000 take 632 ms and 100,000 take 3.9 s of
synchronous work. The same strings without the newline are rejected in
under a millisecond.

An application that validates an attacker-supplied string with these
methods can be stalled by a single long request. The input is rejected
with the correct `AddressError`; the cost of reaching that rejection is
the defect.

##### Details

The constructor in `src/ipv6.ts` removes the CIDR suffix, then the zone,
then checks the length of what is left:

```ts
const zone = constants6.RE_ZONE_STRING.exec(address);

if (zone) {
  this.zone = zone[0];

  address = address.replace(constants6.RE_ZONE_STRING, '');
}

const longest = this.groups * 5 + 5;

if (address.length > longest) {
  throw new AddressError(`IPv6 addresses are at most ${longest} characters.`);
}
```

`RE_ZONE_STRING` is `/%.*$/`. It has no anchor at its start, `.` does
not match a line terminator (`\n`, `\r`, U+2028 or U+2029), and without
the `m` flag `$` matches only at the end of the input. For `%` repeated
N times and then `\n`, the engine starts a match at the first `%`, `.*`
consumes the remaining `%` characters up to the newline, `$` fails
there, and backtracking through every shorter `.*` fails too. The engine
then starts again at the second `%`, and so on: N starts, each
proportional to N. The length limit that follows rejects the string in
constant time, after the scan has already run.

The line terminator need not be last. Any string in which many `%`
characters precede a line terminator behaves the same way.

Every entry point that passes a caller's string to the `Address6`
constructor is affected: `new Address6()`, `isValid()`, both arguments
of `fromAddressAndMask()` and `fromAddressAndWildcardMask()`, and the
prefix argument of `fromAddress4Nat64()` and `toAddress4Nat64()`.
`fromWildcard()` rejects a `%` before it constructs anything,
`fromURL()` admits only hex digits, colons and dots in a host, and
`fromArpa()` checks the nibble grammar first, so those three are
unaffected. `Address4` has no zone and is unaffected.

##### Affected versions

`<= 10.7.3`. The zone pattern has been in the constructor since 1.0.0;
5.9.4, 9.0.5 and 10.7.0 show the same timings as 10.7.3.

##### Impact

`Address6.isValid()` on N `%` characters and a newline, measured on
ip-address 10.7.3 and node 24.21.0:

| Input | Wall time | Same length of `!` |
|---|---|---|
| 5,461 characters | 13 ms | 0.1 ms |
| 16 KiB | 108 ms | 0.1 ms |
| 100 KB | 3.9 s | 0.1 ms |
| 256 KiB | 27 s | 0.2 ms |

The parse is synchronous, so the event loop is blocked for the whole of
the wall time and nothing else on that process is served. No memory is
retained and the process resumes when the call returns.

##### Reachability

The input needs a line terminator after the `%` characters, which
decides where it can arrive. An HTTP header value cannot carry a
carriage return or a line feed, so a host or address taken from a header
does not reach this. A URL can carry both characters percent-encoded at
three bytes each, and Node's default 16 KB limit on the request line and
headers admits about 5,461 of them: 13 ms. A request body is where the
larger sizes come from. Common body parsers default to between 100 KB
and 1 MB, and at 100 KB one field passed to the parser unchecked blocks
the process for 3.9 s.

##### Proof of concept

`npm i ip-address@10.7.3`, then:

```js
const { Address6 } = require('ip-address');

function time(input) {
  const start = process.hrtime.bigint();

  Address6.isValid(input);

  return `${(Number(process.hrtime.bigint() - start) / 1e6).toFixed(1)} ms`;
}

for (const n of [10000, 20000, 40000, 100000]) {
  console.log(`${n}: ${time(`${'%'.repeat(n)}\n`)}, without the newline ${time('%'.repeat(n))}`);
}
```

On affected versions (node 24.21.0):

```
10000: 41.0 ms, without the newline 0.0 ms
20000: 161.1 ms, without the newline 0.0 ms
40000: 632.4 ms, without the newline 0.1 ms
100000: 3899.8 ms, without the newline 0.1 ms
```

Each doubling of the input multiplies the time by four.

##### Remediation

Upgrade to the patched release. In the fix, the constructor finds the
zone by the index of the first `%` and accepts the remainder as a zone
only when it holds no line terminator, which reads the input once. 1 MiB
of the input above is rejected in about a millisecond. Every address
that parsed before parses to the same result, and a string with a line
terminator after a `%` is rejected as it was.

`RE_ZONE_STRING` stays exported from `v6/constants` for code that
imports it directly and is marked `@deprecated`; the library itself does
not call it.

If you cannot upgrade immediately, reject a candidate longer than an
address with a zone identifier can be before you parse it:

```js
if (host.length > 64) throw new Error('not an IP address');
```

#### Severity
- CVSS Score: 6.3 / 10 (Medium)
- Vector String:
`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`

#### References
-
[https://github.com/beaugunderson/ip-address/security/advisories/GHSA-rxp7-6hxx-x8q5](https://redirect.github.com/beaugunderson/ip-address/security/advisories/GHSA-rxp7-6hxx-x8q5)
-
[https://nvd.nist.gov/vuln/detail/CVE-2026-111997](https://nvd.nist.gov/vuln/detail/CVE-2026-111997)
-
[ec80fcd5d7)
-
[https://github.com/beaugunderson/ip-address](https://redirect.github.com/beaugunderson/ip-address)
-
[https://github.com/beaugunderson/ip-address/releases/tag/v10.7.4](https://redirect.github.com/beaugunderson/ip-address/releases/tag/v10.7.4)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-rxp7-6hxx-x8q5) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Nodemailer: A ">" inside a quoted local part ends an angle-addr
early in addressparser, delivering to a domain the header does not name

[GHSA-85x2-q946-cp5h](https://redirect.github.com/advisories/GHSA-85x2-q946-cp5h)

<details>
<summary>More information</summary>

#### Details
##### Vulnerability summary

addressparser ends an angle-addr at the first `>` it sees, including one
inside a quoted local part, a comment or a domain literal. The domain is
then read off the text in front of that `>`. `<"a@evil.com>"@good.com>`
is the mailbox `"a@evil.com>"@good.com` under RFC 5322, and Nodemailer
read it as an address at `evil.com`. The unbracketed spelling of the
same value was already read correctly. Affected: 3.0.0 through 10.1.3.

##### Attacker capabilities

The attacker controls the text of a recipient or sender address that an
application passes to Nodemailer, for example a To value entered in a
contact or invite form, or the header of an inbound message parsed with
mailparser. No access to the application, its configuration or its
credentials is needed. The value is a syntactically valid RFC 5322
address that conformant parsers accept without defects.

##### Realistic exploitation scenario

An application lets users send invitations or notifications only to
addresses at an allowed domain and validates the submitted value with a
conformant parser or by checking its domain. The attacker submits
`<"a@evil.com>"@good.com>`, which validates as a `good.com` mailbox.
Nodemailer then parses the same value, issues `RCPT TO:<"\"a"@evil.com>`
and the message, with whatever content the application puts into it, is
delivered to the attacker's domain. The security boundary crossed is the
application's recipient allow list. In the inbound direction, mailparser
reports a different address than a conformant reader of the same header,
so a display or policy layer built on the two disagrees.

##### Proof of concept

```js
const addressparser = require('nodemailer/lib/addressparser');
console.log(addressparser("<\"a@evil.com>\"@good.com>"));
// [ { address: '"a@evil.com', name: '@good.com>' } ]
```

Python's `email._header_value_parser.get_address_list` reads the same
value as `"a@evil.com>"@good.com`, with no defects reported.

The envelope a message gets is built from the same parse, so `sendMail({
to: "<\"a@evil.com>\"@good.com>" })` issues the RCPT TO shown above.

##### Security impact

Mail that an application intends for an allowed domain is delivered to a
domain chosen by the attacker, which discloses its content. It is a
security vulnerability rather than a parsing bug because the misreading
only occurs for values that a conformant validator approves, so
validation done the right way is bypassed. Affected are applications
that pass user influenced addresses to Nodemailer and consumers of the
standalone parser such as mailparser.

The fix tracks quoted strings, comments and domain literals inside an
angle-addr and reads only a `>` outside them.

Found in an internal review of addressparser on 2026-10-18. Verified on
3.0.0, 6.9.16 and 10.1.3.

#### Severity
- CVSS Score: 6.5 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`

#### References
-
[https://github.com/nodemailer/nodemailer/security/advisories/GHSA-85x2-q946-cp5h](https://redirect.github.com/nodemailer/nodemailer/security/advisories/GHSA-85x2-q946-cp5h)
-
[1cd57d2b8c)
-
[https://github.com/nodemailer/nodemailer](https://redirect.github.com/nodemailer/nodemailer)
-
[https://github.com/nodemailer/nodemailer/releases/tag/v10.1.4](https://redirect.github.com/nodemailer/nodemailer/releases/tag/v10.1.4)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-85x2-q946-cp5h) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Nodemailer: A nested comment ends early in addressparser, releasing
the rest of the comment as a recipient

[GHSA-8c8m-p3m8-cjg8](https://redirect.github.com/advisories/GHSA-8c8m-p3m8-cjg8)

<details>
<summary>More information</summary>

#### Details
##### Vulnerability summary

RFC 5322 comments nest. addressparser ended a comment at the first `)`,
including the one that closes a nested comment, and parsed the rest of
the outer comment as header text. `Victim (x(y) <evil@evil.com>)
<v@victim.com>` names `v@victim.com` with `x(y) <evil@evil.com>` as a
comment, and Nodemailer read it as the address `evil@evil.com`. This is
the same shape as the escaped parenthesis fixed in 10.1.2, reached
through nesting instead of a quoted-pair. Affected: 3.0.0 through
10.1.3.

##### Attacker capabilities

The attacker controls the text of an address that an application passes
to Nodemailer, or the From or To header of an inbound message parsed
with mailparser. No access to the application, its configuration or its
credentials is needed. The value is a syntactically valid RFC 5322
address that conformant parsers accept without defects.

##### Realistic exploitation scenario

An application validates a submitted address with a conformant parser
and allows only its own domain. The attacker submits `Victim (x(y)
<evil@evil.com>) <v@victim.com>`, which validates as `v@victim.com`.
Nodemailer delivers to `evil@evil.com`. In the inbound direction, a
DMARC or display layer built on a conformant parser and a mail client
built on mailparser disagree on the author of the same message, which is
the setting for sender spoofing. The boundary crossed is the
application's recipient allow list, or the author check of the receiving
side.

##### Proof of concept

```js
const addressparser = require('nodemailer/lib/addressparser');
console.log(addressparser("Victim (x(y) <evil@evil.com>) <v@victim.com>"));
// [ { address: 'evil@evil.com', name: 'Victim) v@victim.com' } ]
```

Python's `email._header_value_parser.get_address_list` reads the same
value as `v@victim.com` with the display name `Victim`, with no defects
reported.

The envelope a message gets is built from the same parse, so `sendMail({
to: "Victim (x(y) <evil@evil.com>) <v@victim.com>" })` issues the RCPT
TO shown above.

##### Security impact

Mail intended for an approved recipient is delivered to an attacker
chosen domain, disclosing its content, and parsers built on this module
report a different author than conformant ones. The misreading only
occurs on values a conformant validator approves, so correct validation
is bypassed. Affected are applications that pass user influenced
addresses to Nodemailer and consumers of the standalone parser such as
mailparser.

The fix counts comment depth and ends a comment only at the `)` that
closes the outermost one.

Found in an internal review of addressparser on 2026-10-18. Verified on
3.0.0, 6.9.16 and 10.1.3.

#### Severity
- CVSS Score: 6.5 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`

#### References
-
[https://github.com/nodemailer/nodemailer/security/advisories/GHSA-8c8m-p3m8-cjg8](https://redirect.github.com/nodemailer/nodemailer/security/advisories/GHSA-8c8m-p3m8-cjg8)
-
[0a8761762a)
-
[https://github.com/nodemailer/nodemailer](https://redirect.github.com/nodemailer/nodemailer)
-
[https://github.com/nodemailer/nodemailer/releases/tag/v10.1.4](https://redirect.github.com/nodemailer/nodemailer/releases/tag/v10.1.4)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-8c8m-p3m8-cjg8) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Nodemailer: A ";" inside a quoted string or comment ends an address
group early in addressparser, turning display text into a recipient

[GHSA-m943-m63m-w62w](https://redirect.github.com/advisories/GHSA-m943-m63m-w62w)

<details>
<summary>More information</summary>

#### Details
##### Vulnerability summary

addressparser ends an RFC 5322 group at the first `;`, including one
inside a quoted display name or a comment. The text after it is parsed
again as top level recipients with the quoting flipped, so text that
every conformant parser reads as a display name or comment becomes a
live address. `G: (a; <evil@evil.com>) <v@victim.com>;` names only
`v@victim.com`, and Nodemailer read it as the single recipient
`evil@evil.com`. Affected: 3.0.0 through 10.1.3.

##### Attacker capabilities

The attacker controls the text of an address field that an application
passes to Nodemailer, or the header of an inbound message parsed with
mailparser. No access to the application, its configuration or its
credentials is needed. The value is a syntactically valid RFC 5322 group
that conformant parsers accept without defects.

##### Realistic exploitation scenario

An application validates the recipients of a submitted address list with
a conformant parser and only allows addresses at its own domain. The
attacker submits `G: (a; <evil@evil.com>) <v@victim.com>;`. The
validator sees one mailbox, `v@victim.com`, and approves it. Nodemailer
delivers to `evil@evil.com` only. The same works through a quoted
display name, `G: "a;" "<evil@evil.com>" <v@victim.com>;`. The boundary
crossed is the application's recipient allow list.

##### Proof of concept

```js
const addressparser = require('nodemailer/lib/addressparser');
console.log(addressparser("G: (a; <evil@evil.com>) <v@victim.com>;"));
// [ { name: 'G', group: [ [Object] ] }, { address: 'evil@evil.com', name: ') v@victim.com' } ]
```

Python's `email._header_value_parser.get_address_list` reads the same
value as the single mailbox `v@victim.com`, with no defects reported.

The envelope a message gets is built from the same parse, so `sendMail({
to: "G: (a; <evil@evil.com>) <v@victim.com>;" })` issues the RCPT TO
shown above.

##### Security impact

Mail that an application intends for an approved recipient goes to a
recipient chosen by the attacker, which discloses its content, and the
intended recipient never receives it. The misreading only occurs on
values a conformant validator approves, so correct validation is
bypassed, which makes it a security issue rather than a parsing bug.
Affected are applications that pass user influenced address lists to
Nodemailer and consumers of the standalone parser such as mailparser.

The fix tracks quoted strings and comments inside a group and reads only
a `;` outside them.

Found in an internal review of addressparser on 2026-10-18. Verified on
3.0.0, 6.9.16 and 10.1.3.

#### Severity
- CVSS Score: 6.5 / 10 (Medium)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`

#### References
-
[https://github.com/nodemailer/nodemailer/security/advisories/GHSA-m943-m63m-w62w](https://redirect.github.com/nodemailer/nodemailer/security/advisories/GHSA-m943-m63m-w62w)
-
[1cd57d2b8c)
-
[https://github.com/nodemailer/nodemailer](https://redirect.github.com/nodemailer/nodemailer)
-
[https://github.com/nodemailer/nodemailer/releases/tag/v10.1.4](https://redirect.github.com/nodemailer/nodemailer/releases/tag/v10.1.4)

This data is provided by
[OSV](https://osv.dev/vulnerability/GHSA-m943-m63m-w62w) and the [GitHub
Advisory Database](https://redirect.github.com/github/advisory-database)
([CC-BY
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### qs : qs.stringify with arrayFormat 'comma' throws an uncaught
TypeError on array elements carrying a non-callable own toString (DoS)
[CVE-2026-110816](https://nvd.nist.gov/vuln/detail/CVE-2026-110816) /
[GHSA-6pq8-jhm2-2vcw](https://redirect.github.com/advisories/GHSA-6pq8-jhm2-2vcw)

<details>
<summary>More information</summary>

#### Details
##### Summary

`qs.stringify(obj, { arrayFormat: 'comma' })` throws an uncaught
`TypeError: Cannot convert object to primitive value` when an array in
`obj` contains an element that carries an own, non-callable `toString`
property (for example `{ a: [ { toString: 'x' } ] }`). A remote,
unauthenticated attacker who can influence an object that the
application later re-serializes with the comma array format triggers the
throw. In a service that lacks a synchronous error boundary around the
serialization call, the uncaught exception crashes the worker process,
producing a denial of service.

##### Root Cause

When `arrayFormat: 'comma'` is selected, the comma branch collapses the
whole array into a single value via `Array.prototype.join`, or, under
`encodeValuesOnly: true`, maps each element through the value encoder
before joining. Both paths perform an implicit string coercion
(`ToPrimitive` with hint `"string"`) on each element. For an object
whose own `toString` is a non-callable value, coercion skips the
shadowed non-callable `toString`, falls through to
`Object.prototype.valueOf` (which returns the object rather than a
primitive), and throws. The comma branch runs this coercion before the
per-element null and skip handling in the main loop, so nothing
downstream can neutralize the hostile element, and the throw is never
caught inside the library.

```text
lib/stringify.js  (comma-array branch)
  line 152-154: obj = utils.maybeMap(obj, function (v) { return v == null ? v : encoder(v); });  // encodeValuesOnly path
  line 156:     objKeys = [{ value: obj.length > 0 ? obj.join(',') || null : void undefined }];   // default comma path
lib/utils.js
  line 292:     string = String(str);   // value encoder coercion reached via the encodeValuesOnly path
```

##### Impact

Prerequisites: the application calls `qs.stringify` with `arrayFormat:
'comma'` (a documented, supported option) on an object whose shape can
be influenced by attacker input. Attacker-controllable sources include
`qs.parse(input, { allowPrototypes: true })`, which retains a `toString`
segment (Express 4's default query parser, Express 5's `extended` query
parser, and body-parser's `extended` urlencoded parser all set it),
`qs.parse(input, { plainObjects: true })`, whose null-prototype elements
throw even without a `toString` key (eg, `a[][b]=c`), and `JSON.parse`
of a request body, which needs no qs parse option at all. No
authentication or user interaction is required. Demonstrated capability:
a single request forces an uncaught synchronous `TypeError` in the
serialization call. In a naive single-process Node service with no
synchronous error boundary, this crashes the process and takes the
service offline (availability impact). Under a framework such as Express
that traps synchronous handler throws, the plausible outcome is a
per-request 500 rather than a full outage; that lower-impact case is
noted but not the worst credible supported deployment. There is no
confidentiality or integrity impact, no memory unsafety, and no
prototype pollution.

##### Proof of Concept

`Install qs at the affected version (for example 6.16.0) and run the
following script with Node.js. No network setup is required; it
demonstrates the throw in isolation.`

```js
var qs = require('qs');

// Source A: qs.parse with allowPrototypes retains the hostile toString segment
qs.stringify(qs.parse('a[0][toString]=x', { allowPrototypes: true }), { arrayFormat: 'comma' });

// Source B: a JSON request body, no qs parse option needed
qs.stringify(JSON.parse('{"a":[{"toString":"x"}]}'), { arrayFormat: 'comma' });

// Also affected: the encodeValuesOnly sub-path
qs.stringify(JSON.parse('{"a":[{"toString":"x"}]}'), { arrayFormat: 'comma', encodeValuesOnly: true });
```

```text
A default-join (allowPrototypes) => THREW: TypeError: Cannot convert object to primitive value
B default-join (JSON.parse) => THREW: TypeError: Cannot convert object to primitive value
C encodeValuesOnly path => THREW: TypeError: Cannot convert object to primitive value
N2 callable toString => NO THROW; output="a=z"
N3 isBuffer vector (CVE-2026-82417) => NO THROW; output="a%5Bconstructor%5D%5BisBuffer%5D=x"
qs version: 6.16.0
```

##### Attack Chain

1. **Exposure:** A remote, unauthenticated request reaches an endpoint
whose handler eventually serializes attacker-influenced data with
`qs.stringify(obj, { arrayFormat: 'comma' })`.
2. **Control:** The attacker supplies data that becomes `{ a: [ {
toString: <non-callable value> } ] }`, either via `a[0][toString]=x`
parsed with `allowPrototypes`, or via a JSON body
`{"a":[{"toString":"x"}]}`.
3. **Path:** In `stringify`, the primitive/buffer guard at
`lib/stringify.js:134` is false for an array, so control reaches the
comma branch at `lib/stringify.js:149`.
4. **Guard:** On the `encodeValuesOnly` path, the closure `v == null ? v
: encoder(v)` at `lib/stringify.js:152-154` passes only
`null`/`undefined` through; a non-null object still reaches the encoder.
The default path skips that closure entirely and reaches `obj.join(',')`
at `lib/stringify.js:156` with no guard at all.
5. **Primitive:** The element is coerced to a string
(`Array.prototype.join`, or `String(str)` at `lib/utils.js:292`).
`ToPrimitive` skips the non-callable own `toString`, `valueOf` returns
the object, and a `TypeError` is thrown.
6. **Result:** The uncaught synchronous exception propagates out of the
serialization call, failing the request and, in a service without a
synchronous error boundary, crashing the process (denial of service).

##### Bypass Evidence

This is a different element type on the code path CVE-2026-8723
(GHSA-q8mj-m7cp-5q26) patche

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

---------

Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-10-29 13:45:34 +00:00
Dane - AI (Mastra)
f6cd11f348
chore(deps): lock file maintenance (#28672)
This PR contains the following updates:

| Update | Change |
|---|---|
| lockFileMaintenance | All locks refreshed |

---

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

🔧 This Pull Request updates lock files to use the latest dependency
versions.

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - "before 6am on wednesday"
- 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:eyJjcmVhdGVkSW5WZXIiOiI0NC4xOTAuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjE5MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0aW9uIl19-->

---------

Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-10-29 10:02:15 +00:00
Dane - AI (Mastra)
07c1bf2362
chore(deps): update dependency @ai-sdk/provider-utils@>=3.0.0 <3.0.38 to v3.0.42 (#28773) 2026-10-28 18:08:16 -07:00
Dane - AI (Mastra)
f2ad3844f3
chore(deps): update opentelemetry (#28581)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-10-28 16:48:54 -07:00
shreyas-mastra
6deb7c0a1e
chore(security): Vanta 2026-10-28 - qs 6.16.1, @modelcontextprotocol/node 2.1.1 floors (#28716)
Refs mastra-ai/platform#2931

Vanta remediation pass for 2026-10-28. It follows #28325, which has
merged.

## 2026-10-28 update
Today's live Vanta export added 3 advisory IDs on `mastra-ai/mastra`
(GitHub/Dependabot). This PR fixes the two that have a published fix and
leaves deepmerge, which has none.

| Package | From → To | Finding | Where | How |
|---|---|---|---|---|
| qs | 6.16.0 → 6.16.1 | CVE-2026-110816 / GHSA-6pq8-jhm2-2vcw (Medium
×4) | root `pnpm-lock.yaml`, 9 `e2e-tests/*` lockfiles,
`scripts/gh-issue-triage/package-lock.json` | Raised the existing floors
`qs@>=6.7.0 <6.16.0: 6.16.0` → `<6.16.1: 6.16.1` and `'qs@<6.7.0':
6.16.0` → `6.16.1`. Raised the npm override in gh-issue-triage. |
| @modelcontextprotocol/node | 2.0.0 → 2.1.1 | GHSA-f897-62hf-6gxq (High
×2; HTTP transports had no body-size or batch-length limit) | root
`pnpm-lock.yaml` (published `@mastra/mcp` 1.18.0, used as `mcp-legacy`),
`scripts/gh-issue-triage/package-lock.json` | New pnpm override
`'@modelcontextprotocol/node@>=2.0.0 <2.1.0': 2.1.1` and a new npm
override in gh-issue-triage. I used 2.1.1 rather than 2.1.2 because
2.1.2 needs a `@modelcontextprotocol/server` peer of `^2.4.0`, while
`@mastra/mcp` 1.18 resolves server 2.3.1. `packages/mcp` itself already
uses node 2.1.2. |

- Both versions are older than the 1-day `minimumReleaseAge`: qs 6.16.1
was published 10-14 and node 2.1.1 on 10-02. I did not use qs 6.16.2
(10-27), which is too new.
- No floors or overrides were removed; existing ones were only raised.
- `pnpm install --frozen-lockfile --lockfile-only` passes at the root.
Each nested e2e workspace was regenerated with `pnpm install
--lockfile-only`.
- Added the empty changeset
`.changeset/vanta-2026-10-28-security-floors.md`. No published package
changes.
- After this change, osv-scanner over all 33 lockfiles reports only the
documented leftovers:
  - zod 3.25.76 (zod v3 compat line on purpose)
  - ai 4.3.19 / `@ai-sdk/provider-utils` 2.2.8 (vendored v4 line)
- `@azure/msal-node` 5.6.0 / 6.0.1 (fix 7.1.0 needs majors in identity
and teams)
  - `@opentelemetry/core` 1.30.1 (needs pubsub 6)
  - extract-zip 2.0.1 (no patched release)
- deepmerge 4.3.1 (CVE-2026-93753 / GHSA-gcqx-w48m-w2h4; no patched
release, 4.3.1 is the latest)


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

## ELI5

This PR updates dependency rules and package versions to use newer
releases, including security fixes for `qs` and
`@modelcontextprotocol/node`. It also updates AI SDK dependencies and
does not include published package changes.

## Summary

- Raise the `qs` override target to `6.16.1` in the root and e2e
workspaces and in `scripts/gh-issue-triage`.
- Add an `@modelcontextprotocol/node` override at `2.1.1` in the root
workspace and `scripts/gh-issue-triage`.
- Update AI SDK dependency versions across package manifests and add a
changeset describing the provider-utils update.
- Add an empty changeset for the security-only dependency updates.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

## Update 2026-10-28 (afternoon)
- Merged origin/main (clean).
- Bumped the AI SDK v5 compat line from @ai-sdk/provider-utils 3.0.41 to
3.0.42 (patch, published 2026-10-21; it blocks `.internal` hostnames in
download URL validation and encodes provider-returned IDs in request
paths). This addresses the Aikido /mastra Highs AIKIDO-2026-10990 and
AIKIDO-2026-10981:
- ai 5.0.277 → 5.0.282, @ai-sdk/gateway 2.0.168 → 2.0.173 (vendored
ai_v5)
- anthropic 2.0.109 → 2.0.110, google 2.0.103 → 2.0.106, groq 2.0.58 →
2.0.59, openai 2.0.135 → 2.0.137, openai-compatible 1.0.58 → 1.0.59, xai
2.0.99 → 2.0.100
- Nested lockfiles updated: memory/integration-tests and
playground/e2e/kitchen-sink.
- No new overrides. Changeset:
`vanta-2026-10-28-ai-sdk-v5-provider-utils.md`.
2026-10-28 18:51:27 -04:00
Dane - AI (Mastra)
29747ebd1d
chore(deps): update better-auth monorepo to v1.7.13 (#28538)
This PR contains the following updates:

| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
|
[@better-auth/drizzle-adapter@<1.7.7](https://www.better-auth.com/docs/adapters/drizzle)
([source](https://redirect.github.com/better-auth/better-auth/tree/HEAD/packages/drizzle-adapter))
| pnpm-workspace.overrides | patch | [`1.7.7` →
`1.7.13`](https://renovatebot.com/diffs/npm/@better-auth%2fdrizzle-adapter@<1.7.7/1.7.7/1.7.13)
| `1.7.14` |
| [better-auth](https://better-auth.com)
([source](https://redirect.github.com/better-auth/better-auth/tree/HEAD/packages/better-auth))
| pnpm-workspace.overrides | patch | [`^1.7.7` →
`^1.7.13`](https://renovatebot.com/diffs/npm/better-auth/1.7.7/1.7.13) |
`1.7.14` |
| [better-auth](https://better-auth.com)
([source](https://redirect.github.com/better-auth/better-auth/tree/HEAD/packages/better-auth))
| dependencies | patch | [`^1.7.12` →
`^1.7.13`](https://renovatebot.com/diffs/npm/better-auth/1.7.12/1.7.13)
| `1.7.14` |

---

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

---

### Release Notes

<details>
<summary>better-auth/better-auth
(@&#8203;better-auth/drizzle-adapter@<1.7.7)</summary>

###
[`v1.7.13`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/drizzle-adapter/CHANGELOG.md#1713)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.12...v1.7.13)

###
[`v1.7.12`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/drizzle-adapter/CHANGELOG.md#1712)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.11...v1.7.12)

###
[`v1.7.11`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/drizzle-adapter/CHANGELOG.md#1711)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.10...v1.7.11)

###
[`v1.7.10`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/drizzle-adapter/CHANGELOG.md#1710)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.9...v1.7.10)

###
[`v1.7.9`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/drizzle-adapter/CHANGELOG.md#179)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.8...v1.7.9)

###
[`v1.7.8`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/drizzle-adapter/CHANGELOG.md#178)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.7...v1.7.8)

##### Patch Changes

-
[#&#8203;11512](https://redirect.github.com/better-auth/better-auth/pull/11512)
[`4175b34`](4175b34a8f)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - Align
the installed `@better-auth/utils` version with `better-call` while
accepting `^0.4.2 || ^0.5.0` across official package peers.

-
[#&#8203;11731](https://redirect.github.com/better-auth/better-auth/pull/11731)
[`0cfe07d`](0cfe07dccd)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- Drizzle schemas that store dates in string columns now work:
`timestamp({ mode: "string" })`, MySQL `datetime({ mode: "string" })`,
and SQLite `text()`, including on Cloudflare D1. Before, the adapter
passed a JavaScript `Date` to those columns. Drivers such as
postgres-js, better-sqlite3 and D1 rejected it, so email sign-up, social
sign-in and session refresh failed. Filtering on those columns, for
example when listing sessions, failed the same way. Better Auth now
writes these dates as UTC text and reads a value without a time zone as
UTC.

If your server's time zone is not UTC and you use node-postgres or
mysql2 with a string column that has no time zone, existing rows were
written in the server's local time. They now read back shifted by the
server's UTC offset, so sessions and verification codes created before
the upgrade can expire early or late. Schemas generated by the CLI use
date columns and are unaffected.

</details>

<details>
<summary>better-auth/better-auth (better-auth)</summary>

###
[`v1.7.13`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/better-auth/CHANGELOG.md#1713)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.12...v1.7.13)

##### Patch Changes

-
[#&#8203;11985](https://redirect.github.com/better-auth/better-auth/pull/11985)
[`9cb95fe`](9cb95fe3d0)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - Type
declarations no longer list type-only exports as values, so importing
one as a value now fails type checking instead of failing at runtime.

- Updated dependencies
\[[`2712441`](2712441e35),
[`1cf4b2c`](1cf4b2c8f5)]:
-
[@&#8203;better-auth/core](https://redirect.github.com/better-auth/core)@1.7.13
-
[@&#8203;better-auth/drizzle-adapter](https://redirect.github.com/better-auth/drizzle-adapter)@1.7.13
-
[@&#8203;better-auth/kysely-adapter](https://redirect.github.com/better-auth/kysely-adapter)@1.7.13
-
[@&#8203;better-auth/memory-adapter](https://redirect.github.com/better-auth/memory-adapter)@1.7.13
-
[@&#8203;better-auth/mongo-adapter](https://redirect.github.com/better-auth/mongo-adapter)@1.7.13
-
[@&#8203;better-auth/prisma-adapter](https://redirect.github.com/better-auth/prisma-adapter)@1.7.13
-
[@&#8203;better-auth/telemetry](https://redirect.github.com/better-auth/telemetry)@1.7.13

###
[`v1.7.12`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/better-auth/CHANGELOG.md#1712)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.11...v1.7.12)

##### Patch Changes

-
[#&#8203;11925](https://redirect.github.com/better-auth/better-auth/pull/11925)
[`fb48619`](fb48619083)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - The JWT
plugin now verifies JWTs and session cookie-cache JWTs with the
algorithm of the stored key instead of the one named in the token
header, and logs a warning when it signs or verifies a JWT without an
issuer or audience.

-
[#&#8203;11924](https://redirect.github.com/better-auth/better-auth/pull/11924)
[`681aa5c`](681aa5c443)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! -
`auth.api.getSession()` now keeps the original database error as
`error.cause` when the session lookup fails, so server code can tell a
transient failure from a bug.

-
[#&#8203;11930](https://redirect.github.com/better-auth/better-auth/pull/11930)
[`b18e3b8`](b18e3b8fdf)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - OAuth
callbacks completed through the OAuth proxy now run the same checks as
the standard OAuth callback, including issuer and ID token nonce
validation.

- Updated dependencies
\[[`681aa5c`](681aa5c443),
[`4bc78ba`](4bc78baa83),
[`876608d`](876608da86),
[`083a743`](083a74329b),
[`492134a`](492134aeba)]:
-
[@&#8203;better-auth/core](https://redirect.github.com/better-auth/core)@1.7.12
-
[@&#8203;better-auth/drizzle-adapter](https://redirect.github.com/better-auth/drizzle-adapter)@1.7.12
-
[@&#8203;better-auth/kysely-adapter](https://redirect.github.com/better-auth/kysely-adapter)@1.7.12
-
[@&#8203;better-auth/memory-adapter](https://redirect.github.com/better-auth/memory-adapter)@1.7.12
-
[@&#8203;better-auth/mongo-adapter](https://redirect.github.com/better-auth/mongo-adapter)@1.7.12
-
[@&#8203;better-auth/prisma-adapter](https://redirect.github.com/better-auth/prisma-adapter)@1.7.12
-
[@&#8203;better-auth/telemetry](https://redirect.github.com/better-auth/telemetry)@1.7.12

###
[`v1.7.11`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/better-auth/CHANGELOG.md#1711)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.10...v1.7.11)

##### Patch Changes

-
[#&#8203;10719](https://redirect.github.com/better-auth/better-auth/pull/10719)
[`bd65db0`](bd65db02c1)
Thanks [@&#8203;rendermani](https://redirect.github.com/rendermani)! -
Recognize PostgreSQL `int8` as a valid number type in migration diffs.
Kysely's introspector reports `pg_type.typname`, so Better Auth's own
`bigint` columns (such as the database-backed rate limiter's
`lastRequest`) came back as `int8` and were reported as a type mismatch
on every run.

-
[#&#8203;11521](https://redirect.github.com/better-auth/better-auth/pull/11521)
[`37a75c9`](37a75c95d1)
Thanks [@&#8203;aryan1306](https://redirect.github.com/aryan1306)! - Fix
database-backed rate limiting returning an excessively large
`X-Retry-After` header instead of the remaining seconds in the
rate-limit window.

- Updated dependencies
\[[`ce96569`](ce965696d1),
[`2f6ca3f`](2f6ca3f370),
[`dfd8dd2`](dfd8dd287a)]:
-
[@&#8203;better-auth/core](https://redirect.github.com/better-auth/core)@1.7.11
-
[@&#8203;better-auth/drizzle-adapter](https://redirect.github.com/better-auth/drizzle-adapter)@1.7.11
-
[@&#8203;better-auth/kysely-adapter](https://redirect.github.com/better-auth/kysely-adapter)@1.7.11
-
[@&#8203;better-auth/memory-adapter](https://redirect.github.com/better-auth/memory-adapter)@1.7.11
-
[@&#8203;better-auth/mongo-adapter](https://redirect.github.com/better-auth/mongo-adapter)@1.7.11
-
[@&#8203;better-auth/prisma-adapter](https://redirect.github.com/better-auth/prisma-adapter)@1.7.11
-
[@&#8203;better-auth/telemetry](https://redirect.github.com/better-auth/telemetry)@1.7.11

###
[`v1.7.10`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/better-auth/CHANGELOG.md#1710)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.9...v1.7.10)

##### Patch Changes

-
[#&#8203;11393](https://redirect.github.com/better-auth/better-auth/pull/11393)
[`eebd47a`](eebd47a0e7)
Thanks [@&#8203;breken-ai](https://redirect.github.com/breken-ai)! - If
you use the `lastLoginMethod` plugin with `oneTap`, signing in through
Google One Tap now records `"google"`, the same value as signing in with
the Google button. Before, a One Tap sign-in recorded nothing: the
`better-auth.last_used_login_method` cookie kept its previous value or
stayed unset, and so did `user.lastLoginMethod` with `storeInDatabase`.

If your `customResolveMethod` includes a `/one-tap/callback` →
`"google"` workaround, remove that mapping; keep the resolver if it
handles other routes.

-
[#&#8203;11821](https://redirect.github.com/better-auth/better-auth/pull/11821)
[`09d07e6`](09d07e6fea)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- The Google One Tap prompt (`authClient.oneTap()` without `button`) no
longer calls `getSkippedReason()`, which Google's FedCM migration guide
says to remove. Before, it called it under any `promptOptions.fedCM`
setting.

A skipped prompt now ends the flow and calls `onPromptNotification`
right away instead of retrying. Google doesn't report why a prompt was
skipped, and a prompt the user closed stays hidden for Google's cooldown
period, so the retries could not bring it back. Dismissed prompts still
retry as before.

Google Identity Services still logs its FedCM migration warning, because
it does so whenever `prompt()` receives a listener. The plugin needs the
listener to track dismissals and skips, so the warning is expected and
safe to ignore.

-
[#&#8203;11819](https://redirect.github.com/better-auth/better-auth/pull/11819)
[`eaecb72`](eaecb7229e)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- Google One Tap now applies your
`socialProviders.google.mapProfileToUser` and custom `getUserInfo`, the
same as the standard Google sign-in. Before, One Tap ignored both and
always stored the token's `name`, `email`, `email_verified`, and
`picture` claims.

If you configured either one, users created through One Tap now get the
fields it returns, including any extra fields such as a first name from
`given_name`. Returning users are updated from it on each One Tap
sign-in when `socialProviders.google.overrideUserInfoOnSignIn` is on,
and so are existing users that One Tap links when
`account.accountLinking.updateUserInfoOnLink` is on. Check that your
mapper suits One Tap users too.

If you set `socialProviders.google.overrideUserInfoOnSignIn`, One Tap
sign-ins now update returning users' name, image, and email from Google,
as the redirect sign-in already does.

Setups that configure none of these, including `oneTap({ clientId })`
with no Google provider, are unaffected.

-
[#&#8203;11820](https://redirect.github.com/better-auth/better-auth/pull/11820)
[`88c9a37`](88c9a37856)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- If you set `autoSelect` or `cancelOnTapOutside` on `oneTapClient()`,
the One Tap prompt and the Sign in with Google button now use them.
Before, only values passed to `authClient.oneTap()` took effect, so with
`autoSelect: true` on the plugin, returning users still had to pick an
account. Values passed to `oneTap()` still override the plugin's. Apps
that set these options only on `oneTap()`, or not at all, are
unaffected.

-
[#&#8203;11696](https://redirect.github.com/better-auth/better-auth/pull/11696)
[`0cf1f7c`](0cf1f7c6bc)
Thanks [@&#8203;drewsephski](https://redirect.github.com/drewsephski)! -
You can now import the One Tap plugin from
`better-auth/plugins/one-tap`, as you can for other plugins. Previously
this import failed with a "not exported" error. Imports from
`better-auth/plugins` and `better-auth/client/plugins` are unchanged.

-
[#&#8203;11822](https://redirect.github.com/better-auth/better-auth/pull/11822)
[`414e845`](414e845f12)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- You can now import the Captcha and OpenAPI plugins from
`better-auth/plugins/captcha` and `better-auth/plugins/open-api`, as you
can for other plugins. Previously these imports failed with a "not
exported" error. Imports from `better-auth/plugins` are unchanged.

If your TypeScript config uses `"moduleResolution": "node"` (or
`node10`), `better-auth/plugins/multi-session` and `better-auth/test`
now resolve their types. Previously TypeScript reported that it could
not find their declarations. Projects using `bundler`, `node16`, or
`nodenext` resolution are unaffected.

- Updated dependencies
\[[`fedd055`](fedd05586c),
[`bbd0a19`](bbd0a19c30),
[`99cdfe7`](99cdfe7c2e)]:
-
[@&#8203;better-auth/core](https://redirect.github.com/better-auth/core)@1.7.10
-
[@&#8203;better-auth/mongo-adapter](https://redirect.github.com/better-auth/mongo-adapter)@1.7.10
-
[@&#8203;better-auth/drizzle-adapter](https://redirect.github.com/better-auth/drizzle-adapter)@1.7.10
-
[@&#8203;better-auth/kysely-adapter](https://redirect.github.com/better-auth/kysely-adapter)@1.7.10
-
[@&#8203;better-auth/memory-adapter](https://redirect.github.com/better-auth/memory-adapter)@1.7.10
-
[@&#8203;better-auth/prisma-adapter](https://redirect.github.com/better-auth/prisma-adapter)@1.7.10
-
[@&#8203;better-auth/telemetry](https://redirect.github.com/better-auth/telemetry)@1.7.10

###
[`v1.7.9`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/better-auth/CHANGELOG.md#179)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.8...v1.7.9)

##### Patch Changes

-
[#&#8203;11766](https://redirect.github.com/better-auth/better-auth/pull/11766)
[`6edaa61`](6edaa61e62)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - An
`onAPIError.onError` handler that throws or rejects no longer fails the
request or causes an unhandled promise rejection. The error is logged
and the original error response is returned. Async handlers now finish
before the response is sent.

- Updated dependencies \[]:
-
[@&#8203;better-auth/core](https://redirect.github.com/better-auth/core)@1.7.9
-
[@&#8203;better-auth/drizzle-adapter](https://redirect.github.com/better-auth/drizzle-adapter)@1.7.9
-
[@&#8203;better-auth/kysely-adapter](https://redirect.github.com/better-auth/kysely-adapter)@1.7.9
-
[@&#8203;better-auth/memory-adapter](https://redirect.github.com/better-auth/memory-adapter)@1.7.9
-
[@&#8203;better-auth/mongo-adapter](https://redirect.github.com/better-auth/mongo-adapter)@1.7.9
-
[@&#8203;better-auth/prisma-adapter](https://redirect.github.com/better-auth/prisma-adapter)@1.7.9
-
[@&#8203;better-auth/telemetry](https://redirect.github.com/better-auth/telemetry)@1.7.9

###
[`v1.7.8`](https://redirect.github.com/better-auth/better-auth/blob/HEAD/packages/better-auth/CHANGELOG.md#178)

[Compare
Source](https://redirect.github.com/better-auth/better-auth/compare/v1.7.7...v1.7.8)

##### Patch Changes

-
[#&#8203;11512](https://redirect.github.com/better-auth/better-auth/pull/11512)
[`4175b34`](4175b34a8f)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - Align
the installed `@better-auth/utils` version with `better-call` while
accepting `^0.4.2 || ^0.5.0` across official package peers.

-
[#&#8203;11565](https://redirect.github.com/better-auth/better-auth/pull/11565)
[`b1cfc1e`](b1cfc1ec1e)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - Omit
non-returned custom fields from inferred output schema types.

-
[#&#8203;11540](https://redirect.github.com/better-auth/better-auth/pull/11540)
[`678c555`](678c555beb)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - Align
cookie security attributes with RFC 6265bis.

-
[#&#8203;10591](https://redirect.github.com/better-auth/better-auth/pull/10591)
[`193efff`](193efff3d2)
Thanks [@&#8203;kdelay](https://redirect.github.com/kdelay)! - Expired
or revoked sessions now clear stale cookies when using `customSession`.

-
[#&#8203;11625](https://redirect.github.com/better-auth/better-auth/pull/11625)
[`369176e`](369176e7f6)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- Fixed single-use checks for apps that set
`advanced.database.generateId: "uuid"`. Default id generation is
unaffected, and no migration is needed.

- On SQLite and MySQL, SAML sign-in, DPoP-bound requests checked against
the database replay store, `private_key_jwt` client authentication, and
magic link or email OTP sign-ins that adopt an unverified account failed
with a `NOT NULL` error on the `id` column. They now work. SIWE sign-in
ignored the `email` field and used the wallet-derived address; it now
uses the supplied email when no other account has it.
- On Postgres and MongoDB, a reused SAML assertion, DPoP proof, or
client assertion was accepted. Each one is now accepted only once.

With `generateId: "serial"`, behavior is unchanged: these checks need
string ids, and Better Auth now logs a warning the first time one of
these flows runs.

-
[#&#8203;11391](https://redirect.github.com/better-auth/better-auth/pull/11391)
[`352d04c`](352d04c8eb)
Thanks [@&#8203;breken-ai](https://redirect.github.com/breken-ai)! - Fix
`customSession` treating session lookup failures as signed-out users.
Server-side `getSession` now throws an API error, and HTTP clients
receive an error response.

-
[#&#8203;11750](https://redirect.github.com/better-auth/better-auth/pull/11750)
[`e9d9921`](e9d9921217)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- Generic OAuth providers configured with `discoveryUrl` now recover
without a restart when discovery fails at startup. Since 1.7.3, a
provider whose discovery request failed at boot (for example, because
the identity provider was still starting) was skipped, and every sign-in
returned `PROVIDER_NOT_FOUND` until the app restarted. Better Auth now
retries discovery on the next sign-in, callback, or account-linking
request for that provider, and the provider works as soon as discovery
succeeds. While discovery keeps failing, sign-in and account linking
still return `PROVIDER_NOT_FOUND` and callbacks redirect with
`error=oauth_provider_not_found`, and each request may wait up to 10
seconds for the retry.

-
[#&#8203;11549](https://redirect.github.com/better-auth/better-auth/pull/11549)
[`1bd5c37`](1bd5c37884)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - Fix
`lastLoginMethod` failing sign-in when `cookieName` or `maxAge` is
explicitly `undefined`.

-
[#&#8203;11174](https://redirect.github.com/better-auth/better-auth/pull/11174)
[`766cfb3`](766cfb3f42)
Thanks [@&#8203;Bekacru](https://redirect.github.com/Bekacru)! - Stop
double-decoding `callbackURL`, `newUserCallbackURL` and
`errorCallbackURL` on magic link verify so percent-encoded characters in
callback query params are preserved.

-
[#&#8203;11505](https://redirect.github.com/better-auth/better-auth/pull/11505)
[`c46992f`](c46992f6ce)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! -
Preserve the referenced model and field keys when generating Kysely
migrations, so custom table names that match another model key produce
the intended foreign keys.

-
[#&#8203;11718](https://redirect.github.com/better-auth/better-auth/pull/11718)
[`1d95ebf`](1d95ebf3fe)
Thanks [@&#8203;bytaesu](https://redirect.github.com/bytaesu)! - Fix
missing device sessions and failed automatic session switching after
cache eviction when `storeSessionInDatabase` is enabled and
`preserveSessionInDatabase` is disabled. Automatic switching now follows
the order of held sessions, and large lists or sessions whose users no
longer exist no longer cause valid sessions to disappear.

-
[#&#8203;10266](https://redirect.github.com/better-auth/better-auth/pull/10266)
[`c68b2cd`](c68b2cd8a5)
Thanks [@&#8203;shiminshen](https://redirect.github.com/shiminshen)! -
Projects that enable `exactOptionalPropertyTypes` can use the
`oauthProvider()` and `mcp()` plugins again. Since 1.7.0, adding either
plugin to `betterAuth()` failed to type-check with a TS2322 error.

-
[#&#8203;11637](https://redirect.github.com/better-auth/better-auth/pull/11637)
[`2627237`](2627237fae)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- Projects using the organization plugin with `skipLibCheck: false` no
longer get `TS2536: Type '"role"' cannot be used to index type ...` from
`crud-members.d.mts`. The `role` returned by `getActiveMemberRole` is
now typed as the organization's role names directly. Projects with
`skipLibCheck: true` (the default in most templates) were unaffected.

-
[#&#8203;10866](https://redirect.github.com/better-auth/better-auth/pull/10866)
[`3d1f008`](3d1f008ae3)
Thanks [@&#8203;heliohm](https://redirect.github.com/heliohm)! - The
organization plugin no longer pulls every zod locale into server
bundles.

-
[#&#8203;11626](https://redirect.github.com/better-auth/better-auth/pull/11626)
[`67743ed`](67743ed6e8)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- Password resets and password changes no longer keep the new password
when revoking the user's sessions fails. With
`revokeSessionsOnPasswordReset` or `revokeOtherSessions`, database
sessions are revoked and the password is saved in one transaction when
transactions are enabled for the adapter, so a failure leaves the old
password and sessions in place. Sessions in secondary storage are still
removed after commit, on a best-effort basis. This covers
`/reset-password`, the email OTP and phone number reset endpoints, and
`/change-password`. `onPasswordReset` now runs after sessions are
revoked, so a throwing callback no longer leaves them active, and a
callback that lists the user's sessions no longer sees the revoked ones.

-
[#&#8203;10698](https://redirect.github.com/better-auth/better-auth/pull/10698)
[`f0ce580`](f0ce580fbd)
Thanks
[@&#8203;jashkarangiya](https://redirect.github.com/jashkarangiya)! - If
you set the phone number plugin's `verifyOTP` option,
`/phone-number/reset-password` now checks the code with it, as
`/phone-number/verify` already does. Before, password reset always
compared the code with the one Better Auth generated, so apps that
verify codes through a provider such as Twilio Verify could not reset
passwords. If your `sendPasswordResetOTP` sends the code Better Auth
generates, make sure `verifyOTP` accepts that code. Apps that don't set
`verifyOTP` are unaffected.

-
[#&#8203;11646](https://redirect.github.com/better-auth/better-auth/pull/11646)
[`07a0938`](07a09389ef)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- A failed password reset no longer spends the reset link or OTP.
`/reset-password`, `/email-otp/reset-password` and
`/phone-number/reset-password` now check the token or code without
consuming it, validate and hash the new password, then consume it in the
same transaction as the session revocation and password write. A
rejected password, such as one refused by `haveIBeenPwned`, always
leaves the link or OTP usable. A later failure, such as a failed session
revocation or password write, also leaves it usable when the adapter's
transactions are enabled and verification values are stored in the
database (the default without secondary storage, or
`verification.storeInDatabase: true`). Wrong codes still count against
the OTP attempt limit.

-
[#&#8203;11643](https://redirect.github.com/better-auth/better-auth/pull/11643)
[`92dfcea`](92dfceaa14)
Thanks
[@&#8203;gustavovalverde](https://redirect.github.com/gustavovalverde)!
- A sign-up that fails after its session is created no longer leaves
that session in secondary storage. With `storeSessionInDatabase` enabled
and `preserveSessionInDatabase` off, the secondary-storage copy is
written only after the sign-up commits, and listing a user's sessions
now reads the database, so a session whose cached copy failed to write
is still listed and revoked. With other secondary-storage settings,
sign-up, passkey registration and SSO sign-in with `resolveUser` keep
the session write inside their transaction, so a storage failure rolls
back the new user, passkey or account instead of keeping them without a
session. A session revoked by a `session.create.after` database hook
also stays revoked.

-
[#&#8203;11488](https://redirect.github.com/better-auth/better-auth/pull/11488)
[`e15625f`](e15625ff38)
Thanks [@&#8203;Bekacru](https://redirect.github.com/Bekacru)! -
SvelteKit 3 projects can now install Better Auth without
`--legacy-peer-deps`. The `@sveltejs/kit` peer range now includes
`^3.0.0`; SvelteKit 2 projects are unaffected.

- Updated dependencies
\[[`4175b34`](4175b34a8f),
[`435645e`](435645e5eb),
[`369176e`](369176e7f6),
[`0cfe07d`](0cfe07dccd),
[`9904b29`](9904b29ece),
[`e78f15a`](e78f15aa31),
[`60525e0`](60525e08fd),
[`8133265`](813326536c),
[`ea85d13`](ea85d133d6),
[`916ef5c`](916ef5c530),
[`1d95ebf`](1d95ebf3fe),
[`6214610`](62146108c7),
[`67743ed`](67743ed6e8),
[`c46d2a6`](c46d2a6ac4),
[`92dfcea`](92dfceaa14),
[`a9f455d`](a9f455d586),
[`9725f1b`](9725f1b361)]:
-
[@&#8203;better-auth/core](https://redirect.github.com/better-auth/core)@1.7.8
-
[@&#8203;better-auth/drizzle-adapter](https://redirect.github.com/better-auth/drizzle-adapter)@1.7.8
-
[@&#8203;better-auth/kysely-adapter](https://redirect.github.com/better-auth/kysely-adapter)@1.7.8
-
[@&#8203;better-auth/memory-adapter](https://redirect.github.com/better-auth/memory-adapter)@1.7.8
-
[@&#8203;better-auth/mongo-adapter](https://redirect.github.com/better-auth/mongo-adapter)@1.7.8
-
[@&#8203;better-auth/prisma-adapter](https://redirect.github.com/better-auth/prisma-adapter)@1.7.8
-
[@&#8203;better-auth/telemetry](https://redirect.github.com/better-auth/telemetry)@1.7.8

</details>

---

### Configuration

📅 **Schedule**: (UTC)

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

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

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

🔕 **Ignore**: Close this PR and you won't be reminded about these
updates again.

---

- [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODYuNCIsInVwZGF0ZWRJblZlciI6IjQ0LjE5Mi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0aW9uIl19-->

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-10-28 19:24:36 +00:00
dane-ai-mastra[bot]
6a191d46dc chore: version - exit prerelease mode 2026-10-28 13:15:52 +00:00
Ward Peeters
f1964c0256
ci(e2e): publish a single e2e-test dist-tag for every suite (#28688)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
2026-10-28 14:09:29 +01:00
Damien Schneider
976fde7416
refactor(lint): enable no-else-return at root (#28601)
Enables `no-else-return: error` in the root Oxlint config and removes
186 redundant `else` branches across 111 source/test files. Existing
rule defaults are retained.

Reviewed every code diff for behavior preservation. An independent
TypeScript AST comparison confirms that changes are limited to removing
`else` after returning branches, with the same expressions, statement
order, return values, and `try`/`catch`/`finally` boundaries. All
181,158 identifier occurrences retain their bindings. The recorder
replay path keeps an explicit block: flattening it would shadow the
earlier request `body` with the response `body` and introduce a
temporal-dead-zone error.

Extends the existing monorepo optimized-dependency test to assert that a
raw TypeScript workspace package, including its enum and transitive
dependency, still executes in the production bundle.

Validation: the root rule-only scan passes on 15,273 files with zero
diagnostics; formatting and `git diff --check` pass. Schema
compatibility tests: 1,060 passed, 9 skipped. Recorder runtime tests: 21
passed. The core selection initially passed 3,513 tests; rerunning the
suites requiring local server/cache access passed 185 tests, with one
remaining cache-file assertion also reproduced on unchanged `main`.

Remaining validation limits: four asset-download cases cannot reach
`placehold.co`; the changed-file lint run reports six import-order
errors reproduced on unchanged files from `main`. Deployer unit tests
and the monorepo test could not run because this checkout lacks required
package dependencies (`fs-extra`/workspace links and `get-port`,
respectively). These limits are left visible for CI. No changeset is
included because this is a behavior-preserving lint cleanup.

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

<!-- coderabbit-ai-generated:v1 -->

## ELI5
This PR makes the code easier to read by removing `else` branches that
are not needed after a return. It also enables a rule that catches those
branches and adds a test for loading a raw TypeScript workspace package
in a production bundle.

## Summary
- Enables Oxlint’s `no-else-return` rule at error severity and removes
186 redundant `else` branches across 111 files.
- Extends the monorepo optimized-dependencies test to check a raw
TypeScript workspace package, its enum, and a transitive dependency.
- Updates the deployer’s transpile-package path pattern.
- In workflow event processing, a truthy branch index with no matching
child now falls through to publish a skipped-step end event. Previously,
this case published no event.
- Keeps the recorder replay block explicit to avoid request/response
`body` shadowing and a temporal-dead-zone error.

## Validation
Reported checks passed: the rule-only scan across 15,273 files,
formatting, `git diff --check`, schema compatibility tests (1,060
passed, 9 skipped), recorder runtime tests (21 passed), and an initial
core test selection (3,513 passed).

Some test limits remain. Four asset-download cases could not reach
`placehold.co`. Changed-file lint reported six import-order errors that
also occur on unchanged files from `main`. Deployer unit tests and the
monorepo test could not run because dependencies were unavailable. On
rerun, suites requiring local server/cache access had 185 passes; one
cache-file assertion also reproduced on unchanged `main`.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-10-28 12:30:27 +01:00
Ward Peeters
57d0c3521e
ci(e2e): set snapshot versions directly instead of running changesets (#28683)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-10-28 10:06:24 +01:00
Ward Peeters
29cb6c4867
ci: remove the E2E softwarefactory template job (#28686)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-10-28 10:04:54 +01:00
Ward Peeters
84fa97871a
Validate the checked-in factory templates and retire the generated softwarefactory-template (#28436)
## Summary

`create-factory` now scaffolds the checked-in
`templates/template-factory` (platform) and
`templates/template-factory-self-hosted` (`--no-platform`) starters
(#28430). The old path — generating `mastra-ai/softwarefactory-template`
from `mastracode/web` with `sync-template.mjs` and pushing it from a
dedicated workflow — no longer feeds anything users receive, so this PR
removes it. The new templates sync through the same `sync-templates.yml`
as every other template.

| Before | After |
| --- | --- |
| `sync-softwarefactory-template.yml` generated a template from
`mastracode/web` and pushed it after an install/typecheck/build check
against published npm | Removed. Both factory templates sync through the
shared `sync-templates.yml`, unchanged |
| `e2e-softwarefactory` generated the template, scaffolded it, and
booted it with auth disabled | Scaffolds both checked-in templates
through the built CLI, typechecks and builds them against the local
package set, and boots the self-hosted template against its own Postgres
(`npm run db:up`) behind WorkOS auth |
| Template edits did not trigger the E2E suite | Changes under
`templates/template-factory*` run it |

Also removes `mastracode/mastra-factory/scripts/sync-template.mjs`, its
test, `template/README.md`, and the `template-out` ignores. The suite's
local registry setup is fixed: it could not resolve the verdaccio bin
(verdaccio 6 only exports `.` and `./package.json`) and, because that
failure happened after the repo was snapshot-versioned, left the working
tree mutated.

Stacked on #28430 → #28255.

## Follow-up after release

Once a `create-factory` release that uses the new templates is on
`latest`, archive `mastra-ai/softwarefactory-template` (don't delete it
— older CLI versions still clone it).

## Test plan

- [x] `create-factory`: tests (55), `tsc --noEmit`, lint
- [x] Both templates typecheck and bundle with `mastra build` against
workspace packages
- [x] Self-hosted template boots under `mastra factory dev` against
Postgres: `/signin` serves the Factory UI, `/auth/me` reports `workos`,
`/api/tools` returns 401
- [x] `e2e-softwarefactory` passes locally (7 tests, ~7 min): both
templates scaffold via the built CLI, typecheck, and build against the
local registry; the self-hosted template boots against `npm run db:up`
Postgres
- [ ] `e2e-softwarefactory` passes in CI

---------

Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
2026-10-27 17:06:07 +01:00
Damien Schneider
7dbc6c1d18
refactor(lint): simplify unnecessary template expressions (#28447)
Enable `typescript/no-unnecessary-template-expression` in the shared
TypeScript configuration and simplify 17 redundant interpolations.
Preserve 11 intentional coercions at runtime boundaries and in mock
response text with local explanations. Existing lint scope and package
manifests are unchanged.

Reviewed every edit and compared emitted JavaScript after the approved
string simplifications, including interpolation order and tagged
templates. All 916 function return types and 1,833 variable binding
types in the 21 affected source files are unchanged. CI lint and build
pass; the local 57-task build, CLI typecheck, formatting, and whitespace
checks pass.

Validation covers 193 focused processor, CLI, Couchbase, and GraphRAG
tests, plus 902 deployer tests across the full run and an isolated retry
of one timeout. That protocol-import case passed alone in 14.55 seconds;
unchanged main took 14.61 seconds against its 15-second timeout. Both
selected published-package monorepo E2E cases pass, including the
extended HTTP check for external module resolution. The broad rule audit
found zero rule violations across 15,106 files, alongside four
TypeScript configuration diagnostics in unchanged files; the targeted
scan passes cleanly.

The DuckDB CI job also fails two existing capability-list assertions
because their expected arrays omit `span-aggregate`. Both failures were
reproduced on unchanged base `f4cbdb4d78`; DuckDB and core storage files
are unchanged by this PR.

No changeset is included for this lint maintenance, as requested; the
changeset check is expected to fail. Keep this PR as a draft.


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

## ELI5

This PR adds a check that finds template strings with unnecessary string
insertions. It removes those insertions while preserving explicit
conversions where they may affect behavior.

## Summary

- Enable `typescript/no-unnecessary-template-expression` as an error in
the shared TypeScript configuration.
- Simplify redundant template expressions across CLI, core, deployer,
storage, test, and end-to-end test code.
- Preserve intentional string coercion at runtime boundaries and in mock
responses with local Oxlint suppression comments.
- Keep the existing lint scope and package manifests unchanged,
according to the PR objectives.

## Validation

The PR objectives report passing lint, build, typecheck, formatting,
whitespace, and focused test checks. They also report DuckDB
capability-list failures reproduced on the unchanged base. No changeset
is included as requested. The changeset check is expected to fail.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-10-26 22:37:47 +01:00
shreyas-mastra
34983c9bbb
chore(security): Vanta 2026-10-23/26 - storybook 9.1.21, body-parser, fast-uri, multer, serialize-javascript, zod pins, esbuild/bundle-name overrides (#28325)
## Update 2026-10-26 afternoon (Vanta pass)
Added commit `f6e4b670` on top of the 16:20 ET main merge:
- **esbuild 0.18.20 → 0.25.12** (GHSA-67mh-4wv8-2f99) and **bundle-name
3.0.0 → 4.1.1** (AIKIDO-2026-886499): the 12:43 ET merge of main dropped
the two `pnpm-workspace.yaml` entries this PR added on 10-23
(`'@esbuild-kit/core-utils>esbuild': 0.25.12` and
`'default-browser@4.0.0>bundle-name': 4.1.1`), so both old versions were
back in `pnpm-lock.yaml`. This commit puts them back exactly as before.
No other overrides changed.
- Added the empty changeset
`.changeset/vanta-2026-10-26-afternoon-overrides.md`.
- `pnpm install --frozen-lockfile --lockfile-only` passes.

After this, `osv-scanner` on all 34 lockfiles finds only the documented
leftovers: zod 3.25.76, ai 4.3.19 / `@ai-sdk/provider-utils` 2.2.8 (the
v4 line), extract-zip 2.0.1 (no patch), `@opentelemetry/core` 1.30.1,
and `@azure/msal-node` 5.6.0 / 6.0.1.

---

## Update 2026-10-26 (Vanta pass)
Merged `origin/main` (no conflicts) and added commits `9b169f0f` and
`94e183ff`:

| Package | From → To | Finding | Where | How |
|---|---|---|---|---|
| body-parser | 2.3.0 → 2.4.0 | CVE-2026-111181 / GHSA-27r3-jxmh-p828
(High) | root `pnpm-lock.yaml`, `examples/agent`, refund and genui
templates (npm) | Raised the root floor `body-parser@<2.3.0: 2.3.0` →
`<2.4.0: 2.4.0`. Added a floor in `examples/agent`. `npm update` in the
templates. `patches/body-parser@2.3.0.patch` renamed to `@2.4.0` (same
one-line raw-body interop; it applies cleanly). |
| body-parser | 1.20.6 → 1.20.9 | same advisory, 1.x line | all 10
`e2e-tests/*` lockfiles (verdaccio → express 4) | New floor
`body-parser@<1.20.9: 1.20.9`. The `patches/body-parser@1.20.6.patch`
files are renamed to `@1.20.9` (they apply cleanly). |
| fast-uri | 3.1.8 → 3.1.9 | CVE-2026-110095/-110180/-110306/-110725 |
root, e2e-tests ×10, `examples/agent`, otel-bridge `agent-hub`,
`acp-validator`, `gh-issue-triage`, refund and genui templates | Raised
the existing floors/pins from 3.1.8 to 3.1.9 |
| fast-uri | 4.2.1 → 4.2.3 | GHSA-333x-w4r6-6crp, GHSA-w74x-v6f9-j3xg,
GHSA-wjr9-j795-jxcr, GHSA-xhq7-xmqj-769h | otel-bridge `agent-hub` |
Raised the existing floor `fast-uri@>=4.0.0 <4.1.5: 4.2.1` → `<4.2.3:
4.2.3` |
| multer | 2.4.0 → 2.5.0 | CVE-2026-113872 / GHSA-q7qp-rjg7-q26m (High)
| root | Floor `multer@<2.3.0: 2.4.0` → `multer@<2.5.0: 2.5.0` |
| serialize-javascript | 7.1.2 → 7.1.4 | CVE-2026-115897 /
GHSA-m5mm-p8h7-m29v | root | Floor `<7.0.5: ^7.0.5` → `<7.1.3: ^7.1.3` |
| zod | 4.3.6 / 4.4.3 / 4.5.4 → 4.6.7 | CVE-2023-54404 /
GHSA-mrhx-c7xc-m3w5 (High) | exact pins in
`templates/template-kyc-customer-onboarding`,
`templates/template-security-incident-triage`,
`packages/mcp/integration-tests/{v2,published-v1}`,
`e2e-tests/commonjs/template` | Direct pin bump (same major) |
| fastify | `^5.12.5` → `^5.12.6` | CVE-2026-107832 | devDependency
specifiers in `server-adapters/fastify` and `workflows/inngest` (the
lock already had 5.12.6) | Specifier bump |

- Every new version is older than 24h: body-parser 2.4.0 and 1.20.9
(10-22), multer 2.5.0 (10-22), serialize-javascript 7.1.4 (10-23),
fast-uri 3.1.9 (10-19), fast-uri 4.2.3 (10-19), qs 6.16.1 (10-14, pulled
in by body-parser 2.4.0), zod 4.6.7 (10-12).
- No overrides or floors were removed; the existing ones were only
raised.
- `pnpm install --frozen-lockfile --lockfile-only` passes at the root
and in the nested e2e/example workspaces.
- Added the empty changesets
`.changeset/vanta-2026-10-26-security-floors.md` and
`.changeset/vanta-2026-10-26-fast-uri-4.md`.
- **Not changed:**
- zod 3.25.76: the fix exists only on zod 4, and the zod-v3 support and
compat tests intentionally stay on 3.
- `@azure/msal-node` 5.6.0: the fix is 7.1.0, but `@azure/identity` 4.14
pins `^6` and `@microsoft/teams.apps` 2.1.1 pins `^5.6.0`, so this would
be a two-major runtime jump.
- extract-zip 2.0.1: no patched release (the advisory lists `>=2.0.2`,
which has not been published).
- `@opentelemetry/core` 1.x: needs pubsub 6 / spanner 9, which are
majors.
  - ai v4 / provider-utils: the v4 line is vendored on purpose.

---

Refs mastra-ai/platform#2931

Vanta remediation, 2026-10-23 (follow-up to #28138, which has merged).

| Package | From → To | Finding | Where | How |
|---|---|---|---|---|
| storybook, @storybook/react-vite (+ react, builder-vite, csf-plugin,
react-dom-shim) | 9.1.20 → 9.1.21 | CVE-2026-114125 (Critical),
CVE-2026-114126 (High) | `client-sdks/react` devDependencies | Direct
bump `^9.1.20` → `^9.1.21` |
| esbuild | 0.18.20 → 0.25.12 | GHSA-67mh-4wv8-2f99 | better-auth →
drizzle-kit 0.31.10 → @esbuild-kit/esm-loader → @esbuild-kit/core-utils
(pins `~0.18.20`) | Override `'@esbuild-kit/core-utils>esbuild':
0.25.12` |
| bundle-name | 3.0.0 → 4.1.1 | AIKIDO-2026-886499 | @mastra/deepeval →
deepeval → open@9 → default-browser@4 (pins `^3`) | Override
`'default-browser@4.0.0>bundle-name': 4.1.1` |

### Why there is a `trustPolicyExclude` for storybook 9.1.21
`client-sdks/react` stays on the storybook 9 line; we are not doing the
storybook 10 major here. The only patched 9.x release is 9.1.21. It was
published on 2026-10-12 without the trusted-publisher evidence that
earlier 9.1.x releases had, so `trustPolicy: no-downgrade` fails with
`ERR_PNPM_TRUST_DOWNGRADE`. The exclude covers exactly the six packages
pnpm rejects, each pinned to `@9.1.21`: `@storybook/react-vite`,
`storybook`, `@storybook/react`, `@storybook/builder-vite`,
`@storybook/csf-plugin` and `@storybook/react-dom-shim`. No other
versions or packages are excluded. The packages come from the official
storybook monorepo release, 9.1.21 on the v9 line.

### Notes
- Every new version is older than 24h, so it satisfies
`minimumReleaseAge: 1440`. storybook 9.1.21 is 11 days old, esbuild
0.25.12 is from Nov 2025 and bundle-name 4.1.1 is from 2026-09-25.
- The esbuild override is dev-only: drizzle-kit is a CLI pulled in by
better-auth. I checked that `@esbuild-kit/core-utils` `transform()`
works against esbuild 0.25.12.
- bundle-name 4.x keeps the same `bundleName()` API. It is used only by
`open`'s macOS default-browser lookup.
- `pnpm build-storybook` in `client-sdks/react` fails on main too. The
error is a Babel 8 `loadPartialConfig` error, which happens with 9.1.20
as well, so it is not caused by this PR.
- I ran `pnpm install --frozen-lockfile` and it passes. The changeset is
empty because no published package changes.


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

## ELI5

This PR updates dependency versions and rules that keep older,
reported-vulnerable versions out of the project. It also updates
Storybook and records the changes in changesets.

## Summary

- Raises security-related dependency versions or minimums across the
root project, examples, templates, packages, and e2e workspaces. The
updates include `body-parser`, `fast-uri`, `multer`,
`serialize-javascript`, `zod`, and Fastify.
- Renames `body-parser` patch files and updates workspace references to
match the new versions.
- Updates Storybook packages in `client-sdks/react` from 9.1.20 to
9.1.21. Adds an `esbuild` override and updates the `bundle-name`
override.
- Adds changesets for the dependency updates. No tests were added.

## Validation

The author reports that frozen-lockfile installs pass at the root and in
nested e2e and example workspaces. The author also reports that `pnpm
build-storybook` fails on `main` as well as this branch, with a Babel 8
`loadPartialConfig` error.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-10-26 16:39:13 -04:00
Damien Schneider
f02d3b711e
refactor(lint): remove redundant returns while preserving exits (#28448)
Enable `no-useless-return` in the shared configuration. Remove 28
terminal bare returns, use 31 explicit switch breaks, and retain 12
value-returning contracts with explicit `undefined`. Preserve 13
intentional guards with local explanations, including index-skipping
property reads and the platform availability probe.

Reviewed every edit and checked that removed returns and new switch
breaks have no effectful continuation before function exit, including
cleanup through `finally`. All other source and emitted JavaScript
syntax is preserved apart from formatting, and all 2,020 function return
types and 3,280 variable binding types in the 59 affected source files
are unchanged. The new rule reports zero violations across 15,106 files.
CI lint and build, the local 57-task build, Factory build, core
typecheck, formatting, and whitespace checks pass.

All 756 focused tests pass across stream conversions, idle-loop cleanup,
workflow validation, Factory, Factory UI, Playground UI, Datadog,
Sentry, Cloudflare, and E2B. Both selected published-package monorepo
E2E cases pass. The extended build case covers a missing application
`.npmrc` and verifies successful builds with dependency installation
both skipped and enabled.

The DuckDB CI job also fails two existing capability-list assertions
because their expected arrays omit `span-aggregate`. Both failures were
reproduced on unchanged base `f4cbdb4d78`; DuckDB and core storage files
are unchanged by this PR.

No changeset is included for this lint maintenance, as requested; the
changeset check is expected to fail. Keep this PR as a draft.


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

<!-- coderabbit-ai-generated:v1 -->

## ELI5

This PR teaches the shared lint configuration to flag returns that do
not change what a function does. It updates the affected code so it
still exits at the right point, while keeping returns that are needed to
return a value or protect an intentional guard.

## Summary

- Enables `no-useless-return` as an error in the shared Oxlint
configuration.
- Removes redundant terminal returns, replaces switch-case returns with
`break` where execution continues after the switch, and keeps
value-returning contracts explicit.
- Adds local explanations or lint suppressions for intentional guards.
- Adds assertions that the monorepo build test leaves `.npmrc` files
absent when installation is skipped.

The author reports that source and emitted JavaScript syntax, apart from
formatting, and the return types and variable binding types across all
59 affected files remain unchanged. The author also reports reviewing
changes for effects before function exit, including cleanup through
`finally`.

## Validation and status

The author reports zero violations across 15,106 files and passing CI
lint and build, the local 57-task build, Factory build, core typecheck,
formatting, whitespace checks, 756 focused tests, and two selected
published-package monorepo E2E cases.

The author reports two DuckDB CI failures in existing capability-list
assertions because the expected arrays omit `span-aggregate`. The author
reports reproducing both failures on unchanged base `f4cbdb4d78`; DuckDB
and core storage files were not changed.

No changeset is included, as requested. The author expects the changeset
check to fail and requests that the PR remain a draft.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-10-26 21:03:00 +01:00