mirror of
https://github.com/mastra-ai/mastra.git
synced 2026-11-17 08:44:46 +00:00
224 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
8d4abc4f88 |
chore(deps): Vanta 2026-11-12 — raise undici to 8.12.4 / 7.30.2 (#30205) | ||
|
|
0ffdba0471 |
feat(templates): Add personal assistant template (#29886) | ||
|
|
2b475075a5 |
chore(deps): Vanta 2026-11-11 fixes (effect, fast-xml-parser, react-router-dom, @whatwg-node/fetch) (#30061) | ||
|
|
3cb6caba91 |
chore(templates): tighten Factory template .env.example comments (#28749) | ||
|
|
8a301f6d66 |
chore(deps): force minimatch 11 and glob 14 for Vanta findings (#29916) | ||
|
|
f477d017b5 |
chore(deps): refresh teams.apps and template lockfiles for Vanta findings (#29770)
Lockfile-only refresh for open Vanta / Dependabot findings on mastra. No package.json, override, or resolution changes. | Package | Lockfile | From → To | Finding | |---|---|---|---| | `@microsoft/teams.apps` (via `@chat-adapter/teams`) | `pnpm-lock.yaml` | 2.1.1 → 2.2.0, so `@azure/msal-node` 5.6.0 → 7.x | CVE-2026-109461 (High), Dependabot #3241 | | ws | template-mongodb-bedrock-agent | 8.21.0 → 8.22.1 | AIKIDO-2026-138234 (High) | | protobufjs | template-mongodb-bedrock-agent | 7.6.5 → 7.6.6 | AIKIDO-2026-115254 | | yaml | template-mongodb-bedrock-agent | 2.9.0 → 2.9.1 | AIKIDO-2026-683761 | | jose | template-mongodb-bedrock-agent | 6.2.3 → 6.2.15 | AIKIDO-2026-584205 | | graphql-yoga / `@graphql-yoga/plugin-defer-stream` | template-genui-data-explorer | 5.24.1 / 3.24.1 → 5.24.6 / 3.24.6, which drops nested `@graphql-tools/utils` 11.2.2 | Dependabot #3439, #3441 (High) | `@chat-adapter/teams` already allows `@microsoft/teams.apps ^2.0.14`, and 2.2.0 is the first release that depends on `@azure/msal-node ^7.1.1`. Every version here is more than a day old. Empty changeset: no published package manifest changes. Refs SEC-242, SEC-271 Checked locally: `pnpm install --frozen-lockfile`, plus `@mastra/teams` build, typecheck, and tests. The mongodb template passes `npm ci` and `npm run build`, and the genui template passes `npm install` and `npm run typecheck`. The genui lockfile already fails `npm ci` on main (`@whatwg-node/fetch` override drift). This PR doesn't change that. ## 2026-11-10 update (same PR) Merged `origin/main` ( |
||
|
|
61878201e9 |
chore(templates): make template-agent-harness AGENTS.md concise and warn about outdated training data (#29834) | ||
|
|
b22ffc39a7 |
feat(templates): read the model from AGENT_MODEL in Browser Agent (#29748)
## Description Browser Agent now reads its chat model from `AGENT_MODEL` and falls back to `mastra/openai/gpt-5-mini`, so nothing changes until Mastra Platform sets it. This lets Platform's template form offer a model choice (PLTFRM-3312). Web search now uses the Gateway web search tool from docs-expert instead of OpenAI's provider tool, so it works on any model and the agent's instructions stay true. ## Related issue(s) Linear PLTFRM-3316 ## Type of change - [x] New feature (non-breaking change that adds functionality) ## Checklist - [x] I have linked the related issue(s) in the description above - [x] I have made corresponding changes to the documentation (if applicable) - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR Verified: `mastra build` passes and `tsc` is clean against the published packages. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 The Browser Agent can now use a model selected with `AGENT_MODEL`. If the setting is empty, it uses `mastra/openai/gpt-5-mini`. The agent’s web-search tool uses the Mastra Gateway, regardless of the selected agent model. ## Changes - Added `AGENT_MODEL` and example model IDs to `.env.example`. - Updated the Browser Agent to trim `AGENT_MODEL` and use the default model when the setting is empty. - Added a Gateway-backed `webSearchTool` that returns an answer and deduplicated source URLs. - Removed `@ai-sdk/openai` from the template dependencies. ## Validation - Build and test 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> |
||
|
|
db417615a8 |
feat(templates): use Mastra Connect in the company knowledge template (#29745)
## Description
The company knowledge template now reads Linear and Notion through the
project's Mastra Connect connections instead of `LINEAR_API_KEY` and
`NOTION_API_KEY`. That way, deploying it from Mastra Platform no longer
asks for provider keys. The chat model comes from `AGENT_MODEL` and
defaults to the current Gateway model, so Platform can set it per
project later. Web search uses the Gateway web search tool from
docs-expert, so it works on any model. When a project has more than one
Linear or Notion account connected, indexing covers each one.
```diff
- mcp.ts: MCPClient for mcp.linear.app + @notionhq/notion-mcp-server, keyed by env vars
+ connect.ts: tools({ providers: ['linear', 'notion'] }) when MASTRA_PLATFORM_ACCESS_TOKEN + MASTRA_PROJECT_ID are set
- index-knowledge: raw Linear GraphQL + Notion REST with API keys
+ index-knowledge: linear_list_issues, notion_search_pages, notion_get_page_as_markdown via Connect, per connection
- openai.tools.webSearch (OpenAI models only)
+ tools/web-search.ts (Gateway, any model)
```
## Related issue(s)
Linear PLTFRM-3311. After merge, the template's Platform settings drop
the three env vars and list Linear and Notion as integrations.
## Type of change
- [x] New feature (non-breaking change that adds functionality)
## Checklist
- [x] I have linked the related issue(s) in the description above
- [x] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
Verified: `mastra build` passes and `tsc` is clean against the published
packages. Not run against real Linear and Notion connections yet.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
The template now gets Linear and Notion data through connections in a
Mastra project, instead of asking users for separate service keys. It
also uses Mastra Gateway for web searches and lets users choose the
agent’s model.
## Changes
- Added Mastra Connect tools for Linear and Notion. They load when
platform credentials and a project ID are configured.
- Updated indexing to fetch Linear issues and Notion pages through those
connections.
- Added a Gateway-backed web search tool and an optional `AGENT_MODEL`
setting. The default agent model is `mastra/openai/gpt-5.4`.
- Updated setup documentation and dependencies. Removed the previous MCP
configuration and direct-service API key setup.
## Tests
Build and test 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>
|
||
|
|
76387b0c10 |
feat(templates): read the model from AGENT_MODEL in Personal Agent (#29749)
## Description Personal Agent now reads its chat model from `AGENT_MODEL` and falls back to `mastra/openai/gpt-5.4`, so nothing changes until Mastra Platform sets it. This lets Platform's template form offer a model choice (PLTFRM-3312). ## Related issue(s) Linear PLTFRM-3317 ## Type of change - [x] New feature (non-breaking change that adds functionality) ## Checklist - [x] I have linked the related issue(s) in the description above - [x] I have made corresponding changes to the documentation (if applicable) - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR Verified: `mastra build` passes against the published packages. `tsc` is clean. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 The Personal Agent can now use a model selected through the `AGENT_MODEL` setting. If the setting is empty or unset, the agent uses `mastra/openai/gpt-5.4`. ## Changes - Read and trim `AGENT_MODEL` when the agent starts, then use it as the agent model. - Document `AGENT_MODEL` and example model IDs in `.env.example`. ## Checks Build and type-check results: not available. No tests were added. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
afc9479bdf |
feat(templates): read the model from AGENT_MODEL in Claw Assistant (#29747)
## Description Claw Assistant now reads its chat model from `AGENT_MODEL` and falls back to `mastra/openai/gpt-5.4`, so nothing changes until Mastra Platform sets it. This lets Platform's template form offer a model choice (PLTFRM-3312). Web search now uses the Gateway web search tool from docs-expert instead of OpenAI's provider tool, so it works on any model and the agent's instructions stay true. ## Related issue(s) Linear PLTFRM-3315 ## Type of change - [x] New feature (non-breaking change that adds functionality) ## Checklist - [x] I have linked the related issue(s) in the description above - [x] I have made corresponding changes to the documentation (if applicable) - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR Verified: `mastra build` passes and `tsc` is clean against the published packages. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 Claw Assistant can now use the model named in `AGENT_MODEL`; if the variable is empty or missing, it uses `mastra/openai/gpt-5.4`. Web search uses a separate Gateway tool, so it does not depend on the selected chat model. ## Changes - Documented `AGENT_MODEL` in `.env.example` and the README, including example model IDs and the default. - Added a Gateway web-search tool that sends searches through `openai/gpt-5-mini` with `openrouter:web_search` and returns an answer with deduplicated citations. - Replaced the OpenAI SDK web-search tool with the Gateway tool and removed the `@ai-sdk/openai` dependency. ## Checks - Build and test results: not available. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
5b8c65005c |
feat(templates): read the model from AGENT_MODEL in Docs Expert (#29746)
## Description Docs Expert now reads its chat model from `AGENT_MODEL` and falls back to `mastra/openai/gpt-5-mini`, so nothing changes until Mastra Platform sets it. This lets Platform's template form offer a model choice (PLTFRM-3312). ## Related issue(s) Linear PLTFRM-3314 ## Type of change - [x] New feature (non-breaking change that adds functionality) ## Checklist - [x] I have linked the related issue(s) in the description above - [x] I have made corresponding changes to the documentation (if applicable) - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR Verified: `mastra build` passes against the published packages. `tsc` is clean. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 The Docs Expert template can now use a model chosen through `AGENT_MODEL`. If the setting is missing or contains only whitespace, it uses `mastra/openai/gpt-5-mini`. ## Changes - Added `AGENT_MODEL` to the template’s `.env.example`, with example model IDs and the default. - Updated `docsExpert` to use the trimmed `AGENT_MODEL` value or the default. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
94e5e0dbf2 |
chore(deps): security refresh for templates, examples and integration tests (Vanta) (#29453)
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Dependency updates Refs SEC-256, SEC-261, SEC-262, SEC-263 **2026-11-09:** merged `origin/main` into this branch with a merge commit (no rebase, no force-push). `main` already raised `better-auth` to `^1.7.18` (with its own changeset), so this branch now takes main's version and floors. The old 1.7.16 changeset is removed, and no `better-auth` change is left in this PR. | Package | Where | From → To | Advisory | |---|---|---|---| | chat | `template-genui-data-explorer`, `template-customer-refund-agent` lockfiles (via `@mastra/core`) | 4.41.1 / 4.39.0 → 4.44.0 | AIKIDO-2026-571219 (2026-11-09) | | `@hono/node-server` | `template-customer-refund-agent/client-demo-ui` direct pin | 2.1.5 → 2.1.6 (matches the template's existing 2.1.6 override) | GHSA-jpvv-r467-5p4w and related (2026-11-09) | | next | GenUI template, memory integration tests | 16.4.2/16.4.4 → 16.4.5 | Next.js advisories through 16.4.4 | | fastify | otel-bridge agent-hub | 5.12.6 → 5.12.8 | AIKIDO through 5.12.7 | | shell-quote / proxy-addr / image-size / `@hono/node-server` | MongoDB Bedrock template lockfiles | refreshed (1.12.0 / 2.0.8 / 2.0.4 / 2.1.6) | CVE-2026-102422, CVE-2026-90711, CVE-2025-71329/71330, CVE-2026-118663 | | @opentelemetry/auto-instrumentations-node | MongoDB Bedrock template | ^0.60.0 → ^0.75.0 | CVE-2026-44902 | Empty changeset (`vanta-2026-11-09-template-chat-4-44.md`), because this PR now changes only templates, examples, and integration tests. No published package changes. All versions used were published more than a day ago. No overrides were removed or lowered. Deferred (major-only or no fixed release): extract-zip@2.0.1 (no fix), deepmerge 4.3.1 (no fix), picomatch 4.0.7 (no fix), zod 3.25.76 (fix in 4.x), `@ai-sdk/provider-utils` 2.2.8/3.0.x (fix in 4.0.20+, AI SDK v4/v5 compat lines), ai 4.3.19/5.0.210 (fix in 5.0.52 / 6.0.170), `@azure/msal-node@5.6.0` (7.1.0), minimatch 9/10 (11.0.1), glob 10.5.0/13.0.6 (14.0.2; 13.0.7 is not listed as patched), openai 6.49.0 (7.5.0), `@bufbuild/protobuf@1.10.1` (2.12.1), got 15.1.0 (16.0.0), `@apidevtools/json-schema-ref-parser@11.9.3` (15.5.1), undici 6.29.1 (7.30.1), nanoid 3.3.20 (5.1.16). <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-e7dae54a-e16d-5b3a-ae5d-99ce740a451f?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-e7dae54a-e16d-5b3a-ae5d-99ce740a451f&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 This PR updates several third-party packages to newer versions. The updates include authentication fixes and security-related dependency updates. ## Changes - Updated `better-auth` to `1.7.16` in the workspace, authentication package, and agent example. Added a patch changeset for `@mastra/auth-better-auth` describing session and verification fixes. - Updated `next` to `16.4.5` in the memory integration tests and GenUI data explorer template. - Updated `fastify` to `5.12.8` in the OpenTelemetry bridge example. - Updated OpenTelemetry instrumentation and `zod` in the MongoDB Bedrock agent template. Added scoped `@ai-sdk/provider-utils` overrides and a `compression` override. - Updated the related pnpm and npm lockfiles. ## Validation Build and test results: not available. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: shreyas-mastra <shreyas-mastra@users.noreply.github.com> |
||
|
|
1657c2f82a |
feat(templates): add MongoDB and AWS Bedrock agent template (#29408)
## Description Adds `template-mongodb-bedrock-agent`, an official Mastra template developed by a Mastra team member in collaboration with partners. The template provides a documentation assistant using MongoDB Atlas for vector search and conversation storage, Amazon Bedrock for Claude responses and Titan embeddings, and Amazon Bedrock AgentCore for deployment. Includes document ingestion, Docker and CDK configuration, setup documentation, and a patch for the Bedrock provider. Validation completed: repository formatting checks with `oxfmt`, TypeScript builds for the agent and CDK project, and the existing CDK synthesis test. Live MongoDB/Bedrock ingestion and AgentCore deployment were not rerun for this import. ## Related issue(s) There is no linked issue because this template is a new feature developed as an official Mastra template in collaboration with partners. ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [ ] Test update ## Checklist - [ ] I have linked the related issue(s) in the description above - [x] I have made corresponding changes to the documentation (if applicable) - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 This PR adds a ready-to-use assistant that answers questions about Mastra documentation. It stores documents and conversation history in MongoDB, uses Amazon Bedrock to find and write answers, and includes files to deploy the assistant to AgentCore. ## What changed - Added an official template with setup, customization, and deployment instructions. - Added a script that fetches Mastra documentation, creates embeddings, and stores searchable chunks in MongoDB Atlas. After a successful run, it removes outdated chunks from the Mastra documentation corpus. - Added a search tool and documentation agent that use Bedrock models and MongoDB-backed conversation memory. - Added an AgentCore HTTP entrypoint with health checks, request validation, upload limits, and memory scoped to the platform-provided user and session. - Added MongoDB configuration that uses `MONGODB_URI` locally or retrieves the URI from AWS Secrets Manager when deployed. - Added Docker and CDK deployment configuration, tests, and a patch for the Amazon Bedrock provider. - Pinned the AgentCore CLI to `0.31.1`. ## Validation The author reports that `oxfmt`, TypeScript builds for the agent and CDK project, and the CDK synthesis test completed. The author did not rerun live MongoDB/Bedrock ingestion or AgentCore deployment for this import. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Alex Booker <booker@booker.codes> |
||
|
|
b6dd5da728 |
chore(deps): bump @google-cloud/spanner, better-auth and follow-redirects (#29052) | ||
|
|
f0ad164646 |
chore(security): Vanta 2026-11-02 - @hono/node-server 2.1.6 (MCP SDK/templates), graphql-scalars 2.0.1, raw-body 4, jose 6 (overrides) (#29199) | ||
|
|
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 (@​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 [@​hi-ogawa](https://redirect.github.com/hi-ogawa), **Hiroshi Ogawa** and **Claude Opus 5.5** in [#​11578](https://redirect.github.com/vitest-dev/vitest/issues/11578) [<samp>(28dc1)</samp>]( |
||
|
|
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>
|
||
|
|
e35d500c14 |
chore(security): Vanta 2026-10-29 - systeminformation 5.33.16, re2js 2.8.8, provider-utils 3.0.42 (nested lockfiles) (#28852) | ||
|
|
f36e4f469a |
Let MastraFactory pick the sandbox in the platform factory template (#28603)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
b5bce97c24 |
feat(templates): add insurance policy checking (#28484)
## Description Adds an official Insurance Policy Checking template for brokers to compare issued policies with accepted proposals or contracts. Users upload PDFs in Mastra Studio, identify the agreed terms and any supporting amendments, inspect findings with source evidence, and review a versioned PDF report before approving it. Confirmed discrepancies can produce a proposed correction request for manual delivery. The template includes local document storage, configurable processing budgets, broker review through a suspend/resume workflow, sample PDFs, a usage walkthrough, and unit, integration, and Studio end-to-end tests. Scope is limited to `templates/template-insurance-policy-checking`; there are no changes to framework packages. **Mastra dependencies intentionally use `latest`.** `@mastra/core`, `@mastra/libsql`, and `@mastra/memory` are set to `"latest"`, as is the `mastra` devDependency. This follows the explicit requirements in the [template contribution guide](https://github.com/mastra-ai/mastra/blob/main/templates/README.md). ## Related issue(s) The issue requirement is waived for this PR: this is a new official template developed by a member of the Mastra organization. ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [x] Test update ## Checklist - [x] The related issue requirement is waived, as explained above - [x] I have made corresponding changes to the documentation - [x] I have added tests that cover the feature - [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 adds a template that helps brokers check whether an issued insurance policy matches the terms they agreed to. It shows findings with evidence, lets brokers review and approve a specific report version, and can prepare a correction request for confirmed differences. ## Summary - Adds `templates/template-insurance-policy-checking`, with setup and usage guides, sample documents, and configurable input and processing limits. - Adds PDF intake, evidence-backed comparison, versioned reports, broker review and approval, and proposed correction requests. - Adds local storage and recovery, provider configuration, and processing-budget controls. - Adds unit, integration, evaluation, and Studio end-to-end test suites. Test execution results and review finding counts are not available in the supplied evidence. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
5d4d9c7b88 |
feat(templates): add accounts payable invoice processing (#28532)
## Description Adds the official Accounts Payable Invoice Processing template to the Mastra monorepo. It extracts invoice data from PDFs and images, validates vendors, matches purchase orders, detects duplicates, and routes approvals through a persistent workflow. Includes a QuickBooks MCP adapter for optional bill posting, setup documentation, local tests, and a sandbox integration suite. All `@mastra/*` dependencies and the `mastra` devDependency explicitly use `"latest"`, following the requirements in [templates/README.md](https://github.com/mastra-ai/mastra/blob/main/templates/README.md#required-files). ## Related issue(s) The issue requirement is waived for this contribution. This is a new feature integrating an official template already published in the [Mastra template catalog](https://mastra.ai/templates/accounts-payable-automated-invoice-processing) into the monorepo. ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [x] Test update ## Checklist - [x] Related issue requirement waived as explained 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 - [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 adds a template that helps a business check invoices before paying them. It checks invoice details against vendor and purchase-order records, sends invoices that need review to an approver, and can post approved bills to QuickBooks when configured. ## What changed - Added an Accounts Payable Invoice Processing template to the Mastra monorepo. - Added invoice validation and workflow controls for vendor checks, purchase-order matching, duplicate detection, and policy-based routing. - Added authenticated approval and rejection. Each decision is bound to the workflow run and invoice digest. - Added signing-key-based approval proofs that can survive process restarts. Without a configured signing key, the development key is process-random, so pending decisions may not survive a restart. - Added an optional QuickBooks MCP provider for accounting searches and bill posting. Posting is disabled by default and requires explicit configuration. - Added setup and contribution documentation, environment examples, and lint and formatting configuration. - Added unit and workflow tests, including process-restart coverage for approval and rejection, plus an optional live QuickBooks sandbox integration suite. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
1001dcc4a8 |
Add template-factory starter for the software factory (#28255)
## Summary - Adds `templates/template-factory`, a starter that deploys the Mastra software factory to the platform. - `src/mastra/index.ts` configures `MastraFactory` with a `PlatformSandbox` and repo templates, and requires `DATABASE_URL` outside local development. - The package declares the `@mastra/core` and `@mastra/platform-workspace` dependencies that the entry imports directly. ## Test plan - Confirmed `PlatformSandbox` and `createRepoTemplate` are exported from `@mastra/platform-workspace`. - Not yet run end to end: start with `pnpm dev` against a Postgres `DATABASE_URL` and the platform env vars. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 This PR adds two starter projects for Mastra Factory, which helps coding agents work on software issues. One starter uses platform services when deployed; the other runs its services on infrastructure you manage. ## Changes - Adds `templates/template-factory` with setup documentation, package scripts, and deployment configuration. It requires `DATABASE_URL` and `FACTORY_CREDENTIAL_ENCRYPTION_KEY`, uses PostgreSQL for storage and vectors, and passes `MASTRACODE_PUBLIC_URL` for deployed sign-in links. It uses local sandboxes in development and platform sandboxes otherwise. - Adds `templates/template-factory-self-hosted` with WorkOS authentication, PostgreSQL storage and vectors, GitHub App integration, credential encryption, and a local sandbox. Its entry point requires the database URL, WorkOS cookie password, credential-encryption key, and GitHub App settings. - Adds Docker Compose configuration and `db:up` and `db:down` scripts for the self-hosted starter’s local PostgreSQL database. - Both entry points prepare and finalize `MastraFactory`, then export a configured `Mastra` instance. ## Testing End-to-end testing has not been run. The reported test plan is to start the platform starter with `pnpm dev`, a PostgreSQL `DATABASE_URL`, and the required platform environment variables. No other test results were supplied. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
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 ` |
||
|
|
be82e8d1b5 |
security: Vanta remediation (2026-10-22 → 2026-10-23: storybook, vitest 4.1.12, toml 5.0.1, fastify, ip-address) (#28138) | ||
|
|
323c14179f |
chore(security): bump Node.js to 22.23.4 / 24.22.1 (CVE-2026-111497) (#28170)
Node.js Oct 2026 security release (v22.23.4 / v24.22.1): fixes Brotli
OOB write RCE CVE-2026-111497, TLS hostname-verification bypasses, dns
NUL truncation, eMudhra CA distrust, undici/OpenSSL/c-ares updates.
Bumps the Node pins in this repo: 24.22.1 for CI and the default E2B
template, 24.22.1 and 22.23.4 for the starter templates and the
otel-bridge example. `node:22-*` image tags stay floating, so they
resolve to the patched release on their own, and engine ranges are
unchanged.
⚠️ 24h soak rule: nodejs.org dist published 2026-10-21 10:33 UTC. Docker
`node:22.23.4-slim`/`-bookworm-slim` published 2026-10-21 17:38 UTC (24h
at 1:38 PM EDT Oct 22); `node:22.23.4-alpine` published 2026-10-22 02:39
UTC (24h at 10:39 PM EDT Oct 22). Do not merge before then.
After merge, images must be rebuilt and redeployed for the fix to take
effect.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This PR updates Node.js versions used by CI, templates, and E2B sandbox
defaults. It brings them to the versions identified in the PR
description as security updates.
## Changes
- Updates Node.js 24 pins in GitHub Actions workflows and the setup
action from `24.22.0` to `24.22.1`.
- Updates the default Node.js version for E2B templates to `24.22.1`.
- Updates Node.js pins in two templates and an observability example to
`22.23.4` or `24.22.1`.
- Adds a test for the E2B default template’s version-based identity and
a patch changeset for `@mastra/e2b`.
The supplied change summary does not confirm updates to floating
`node:22-*` tags. It does not provide test results or current review
findings.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Justin Levine <20596508+jal-co@users.noreply.github.com>
|
||
|
|
80c6d4f769 |
chore: refresh hardcoded model router defaults to latest models (#28108) | ||
|
|
a15ea70e71 |
security: Vanta remediation (2026-10-21) (#28018) | ||
|
|
6e178c365a |
docs: declare node types in tsconfig examples (#27974) | ||
|
|
ec35d91a79 |
feat(templates): add lead qualification template (#27839)
## Description Adds `template-lead-qualification`, an official Mastra template for researching companies and qualifying incoming leads against a configurable ideal customer profile (ICP). Supports JSON API or Attio intake, source-backed research through OpenAI, deterministic scoring, and human review for uncertain results. Includes durable workflow recovery, local Markdown reports or Attio output, telemetry, evaluation tooling, documentation, and a demo. **All `@mastra/*` packages and the `mastra` CLI use `"latest"`, following the explicit requirements in the [official templates README](https://github.com/mastra-ai/mastra/blob/main/templates/README.md).** Includes unit and integration tests covering intake, qualification, evidence validation, human review, Attio adapters, recovery, evaluation, and telemetry. ## Related issue(s) The issue requirement is waived for this contribution: this is a new feature delivered as an official Mastra template and developed by a member of the Mastra organization. ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [x] Test update ## Checklist - [x] Related issue requirement waived for this contribution (see 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 - [x] I have addressed all Coderabbit comments on this PR <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 This PR adds a ready-to-use Mastra template that checks whether new company leads match a configurable ideal customer profile. It researches companies, scores leads, requests human review when needed, and safely recovers after interruptions. ## Summary - Adds the official `template-lead-qualification` template. - Supports JSON API and Attio intake, with local Markdown or Attio output. - Adds OpenAI-backed research with source, citation, domain, and evidence validation. - Adds deterministic scoring for business model, employee count, headquarters, and buying intent. - Adds human review, approval, reopening, conflict handling, and output reconciliation. - Adds durable storage, retries, idempotency, restart recovery, and uncertain-write recovery. - Adds privacy-filtered telemetry, evaluation tooling, quality fixtures, reporting, and retention maintenance. - Adds Attio setup tooling, webhook authentication, mapping validation, and migration support. - Adds documentation, demos, and unit and integration tests. - Documents the requirement to use `"latest"` for `@mastra/*` packages and the `mastra` CLI. ## Validation Recent changes also address dispatch after input-drain failures, rejected-evidence isolation, internationalized email domains, report ordering, diagnostic URL stability, maintenance CLI locking, and semantic evaluation reviews. Test execution results are not available in the supplied evidence. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Alex Booker <booker@booker.codes> |
||
|
|
f3cf77305f |
security: Vanta remediation (2026-10-20) (#27828) | ||
|
|
fa409d430b |
security: Vanta remediation pass 2026-10-14/15/19 (zod 4.6.7, @ai-sdk/provider-utils, @copilotkit template) (#27023) | ||
|
|
6bfe7087fc |
fix(core): accept refusal answers from classifier decision models (#27488) | ||
|
|
380dfd6587 |
feat(templates): read AGENT_INSTRUCTIONS and AGENT_MODEL in starter agent (#27282) | ||
|
|
24381fc938 |
feat(template-starter-agent): name the agent from AGENT_NAME (#27039)
## Why Platform onboarding now lets users name their starter agent and sets that name as `AGENT_NAME` on the starter project (mastra-ai/platform#3522). The template hardcoded "Starter Agent", so Studio and the agent's replies ignored it. ## What changed - `agentName` reads `AGENT_NAME` and falls back to "Starter Agent" when it's unset or blank. The agent's display name, the first line of its system prompt, and the static welcome message use it. - The agent id stays `agent`, so existing threads, Connect channels, and the welcome thread still resolve. - `.env.example` documents `AGENT_NAME`. ## Scope Bot display names in Slack, Discord, and Telegram are out of scope. A Studio edit to the system prompt replaces the name line along with the rest of the prompt. ## Verification - `tsc --noEmit` passes on a fresh install of the template. - Loaded the agent with `AGENT_NAME="Support triage"`: name "Support triage", prompt starts "You are Support triage". Unset, empty, and whitespace-only values all give "Starter Agent". The id stays `agent` in every case. Fixes PLTFRM-2657 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 You can set a name for the starter agent with `AGENT_NAME`. If the value is missing or blank, it uses “Starter Agent.” ## Summary - Use the trimmed `AGENT_NAME` value for the agent’s display name and the opening line of its system prompt. Keep the agent ID as `agent`. - Use the configured name in the static welcome message and its Studio navigation instructions. - Document `AGENT_NAME` in `.env.example` as an optional setting. Test results were not provided. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
9d94cffd5b |
feat(templates): add vendor risk questionnaire (#26924)
## Description Adds the official Vendor Risk Questionnaire template, created by Mastra member, in `templates/template-vendor-risk-questionnaire`. Mastra workflows handle XLSX/DOCX intake, draft answers from approved local evidence with citations, and require human review and approval before exporting the completed questionnaire in its original format. Includes a Svelte web demo, CLI tools, local persistence, review metrics, setup guides, and automated unit, integration, security, and evaluation tests. ## Related issue(s) Not applicable. This is a new official Mastra template created by a team member; no associated issue is required. ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [ ] Test update ## Checklist - [ ] I have linked the related issue(s) in the description above — N/A for this team-authored official template. - [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 - [x] I have addressed all Coderabbit comments on this PR Tests are included in the branch; they were not rerun while preparing this PR description. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 This PR adds a tool to help teams answer vendor security questionnaires using approved company documents. It drafts answers with citations, then asks a person to review and approve them before filling in and returning the original XLSX or DOCX file. ## Summary - Adds a Vendor Risk Questionnaire template with a Svelte demo, CLI tools, setup guides, local persistence, metrics, and automated tests. - Supports XLSX and DOCX questionnaires, with evidence in Markdown, JSON, CSV, PDF, and XLSX formats. - Validates questionnaire mappings, source files, evidence scope, citations, and answer destinations before processing or export. - Uses bounded, screened AI workflows to draft answers from approved evidence. Unsupported answers can be marked unknown or routed for review. - Requires human review and approval before export. The export preserves the original document and updates approved answer fields. - Adds run cancellation and resumption, database writer ownership and recovery, review metrics, and privacy-filtered observability. ## Validation The PR description says tests were not rerun while preparing it. Current test results are not provided. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
de08e3033a |
fix(templates): prevent slow email redaction on long log strings (#26620)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
4573441fde |
fix(deps): Vanta 2026-10-09 security updates (handlebars, hono, follow-redirects, @whatwg-node/fetch) (#26532) | ||
|
|
9241d454c6 |
fix(template-genui-data-explorer): use absolute README links (#26414)
## Description **This PR only fixes links in the GenUI Data Explorer README.** Replace four relative links with absolute URLs to the documentation and contribution guide in the Mastra monorepo so they work from the [published template page](https://mastra.ai/templates/genui-data-explorer). No application code, dependencies, or runtime behavior changes. Verified all four target paths against upstream main. README formatting and Git whitespace checks passed, and an independent review found no issues. ## Related issue(s) No linked issue; this is a README-only link correction. ## 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) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [ ] Test update ## Checklist - [ ] I have linked the related issue(s) in the description above - [x] I have made corresponding changes to the documentation (if applicable) - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR |
||
|
|
f2412328d1 |
feat(templates): add Competitor Monitor with Jev (#26353)
## Description Adds the existing official Competitor Monitor with Jev template to `templates/template-competitor-monitor-jev` in the Mastra monorepo. This template is already published in the official catalog: https://mastra.ai/templates/competitor-monitor-jev Users provide competitor URLs and monitoring interests through Mastra Studio chat. Native workflows collect public pages, persist baselines, compare subsequent captures, and classify changes with Jev while retaining source links and before-and-after evidence. Includes conversation memory, browser fallback, optional daily schedules, Markdown notifications, documentation, and tests. Validation: - 112 automated tests passed, including Chrome browser tests. - TypeScript checks, production build, and formatting checks for committed files passed. - Live OpenAI chat collected three Resend pages and created baselines. - A new conversation recovered the saved configuration and completed another check. - A real Jev request through Vercel AI Gateway succeeded using a labeled synthetic pricing example. Live validation did not cover an actual website change through classification or scheduled notification delivery. The dedicated live-evaluation suite requires separate operator-supplied inputs and Studio execution records. ## Related issue(s) No separate issue is linked. This is a new template contribution proposed by a Mastra team member to bring an already-published official template into the monorepo. Published template: https://mastra.ai/templates/competitor-monitor-jev ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [x] Test update ## Checklist - [x] I have provided the contribution context and linked the published official template above - [x] I have made corresponding changes to the documentation - [x] I have added tests that prove the feature works - [x] I have addressed all Coderabbit comments on this PR <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 This template helps teams track changes on public competitor pages. It saves an earlier version, compares new versions, and uses Jev to identify changes that may matter. ## Summary - Adds a Mastra Studio chat agent to configure monitors and start checks. - Collects public pages, saves baselines, and records changes with source links and before-and-after evidence. - Uses Jev to classify changes and routes uncertain cases for review. - Adds persistent storage, conversation memory, browser rendering fallback, optional daily schedules, and Markdown notifications. - Adds setup documentation, configuration examples, and automated tests for collection, classification, storage, scheduling, and reporting. The PR objectives report 112 automated tests passed, along with TypeScript, production build, and formatting checks. They also report live checks for page collection, baseline creation, configuration recovery, and a synthetic Jev pricing example. Live validation did not cover classification of an actual website change or scheduled notification delivery. Follow-up commit reports cite 124 non-live tests passing, plus TypeScript, build, and formatting checks. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Alex Booker <booker@booker.codes> |
||
|
|
446a2843a9 |
feat(templates): add generative UI data explorer template (#26333)
## Description Adds a standalone data explorer template demonstrating generative UI with Mastra and CopilotKit. Users ask questions in a Next.js chat, and the agent selects React components to present verified answers as metric cards, tables, charts, and cohort heatmaps. The template includes 24 complete months of synthetic B2B SaaS Sales data in SQLite, generated during initial setup and preserved across restarts. It supports filtering, comparisons, drill-down, corrections, and persistent chat history. Data-source adapters and the component catalog can be extended independently. All changes are contained in `templates/template-genui-data-explorer`. The template includes setup and extension documentation, local NPM tooling, deterministic Mastra evaluations, and browser tests. It targets a local single-user workspace; remote UI access requires an authentication gateway. Validation: - Formatting, TypeScript checks, and production builds passed. - 13 unit tests and 59 integration tests passed. - Eight deterministic evaluation dimensions passed. - Browser and standalone packaging suites passed in the previous validation round; they were not rerun for this schema refactor. - No paid-provider benchmark was run. Known dependency limitation: the audit reports 19 affected package entries, including six high-severity entries in development dependencies. The production audit reports 12 entries with no high or critical findings. Remaining advisories involve `braces`, `sprintf-js`, and AI SDK provider utilities; no compatible patched replacements were found. ## Related issue(s) No linked issue. This PR proposes a new standalone template. ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [x] Test update ## Checklist - [ ] 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 - [x] I have addressed all Coderabbit comments on this PR <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 This PR adds a ready-to-run explorer where users can ask questions about sample sales data and see answers as charts, tables, and cards. It checks the data behind each answer and saves chat sessions so users can return to them. ## What changed - Added a standalone Next.js and Mastra template that creates and retains a synthetic SQLite sales dataset. - Added a data-source framework and a Sales adapter for bookings, conversion, growth, pipeline, forecasts, churn, and customer cohorts. - Added schema validation for Sales filters and monthly periods before worker execution. Runtime coverage checks remain in place, and invalid input returns an error. - Added checks that validate source results and component choices before the UI displays them. - Added saved chat sessions, filters, comparisons, drill-downs, corrections, and persistent views. - Added metric cards, tables, charts, and cohort heatmaps, with documentation for extending data sources and UI components. - Added launch and proxy tooling, workspace access controls, telemetry, deterministic evaluations, and unit, integration, and browser test suites. ## Validation and reported status The PR objectives report passing formatting and TypeScript checks, 13 unit tests, 59 integration tests, 16 workspace browser tests, five quality and packaging tests, and eight deterministic evaluation dimensions. They also report a fresh standalone installation, production build, and two standalone browser scenarios. No paid-provider benchmark was run during final validation. The objectives report 19 affected package audit entries, including six high-severity development dependency entries. They report 12 production audit entries and no high or critical production findings. Remaining advisories involve `braces`, `sprintf-js`, and AI SDK provider utilities. Review severity counts are unavailable because current review findings were not supplied. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Alex Booker <booker@booker.codes> |
||
|
|
73398a7a00 |
fix(template-starter-agent): ship local gateway-backed web_search tool (#26288)
## Summary
The starter template was importing `webSearchTool` from
`@mastra/core/tools`, which is a provider-executed placeholder that only
runs on OpenAI, Anthropic, Google, and xAI. On every other model the
agent's search call fails with `WEB_SEARCH_UNSUPPORTED_PROVIDER`.
Ports the gateway-backed web search tool from `template-docs-expert`: a
local `createTool` that posts to the Mastra Gateway's `chat/completions`
endpoint with `openrouter:web_search`. The gateway runs the search
server-side and returns the answer plus citation annotations, so the
agent model only needs tool-calling support (nothing provider-specific).
## Changes
- Add `src/mastra/tools/web-search.ts` (gateway-backed `web_search`
tool, output: `{ answer, sources[] }`).
- Swap `webSearchTool` import in `src/mastra/agents/agent.ts` from
`@mastra/core/tools` to the local file.
## Test plan
- `npm install` clean (template installs against `latest` dist-tags).
- `npx tsc --noEmit` clean.
- Works with any gateway-routed model; follow-up can revisit the
`gpt-6-luna` default from #26266 if we want a cheaper tool-capable
model.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
The starter agent now uses a local web-search tool that sends searches
through the Mastra Gateway. This lets the agent use web search even when
its own model does not support a provider-specific search tool.
## Changes
- Added `webSearchTool` in
`templates/template-starter-agent/src/mastra/tools/web-search.ts`. It
sends queries to the Gateway’s chat-completions endpoint with
`openai/gpt-5-mini` and `openrouter:web_search`.
- The tool returns an answer and deduplicated citation sources. It
accepts `MASTRA_GATEWAY_URL` and requires `MASTRA_GATEWAY_API_KEY`.
- Updated the starter agent to use the local tool instead of the
imported `@mastra/core/tools` web-search tool. The other core tools
remain unchanged.
- Added a patch changeset for `template-starter-agent`.
## Validation
The PR description reports successful `npm install` and `npx tsc
--noEmit`. It does not provide a test command or results for the
reported behavior across gateway-routed models.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
|
||
|
|
ea7ca755a4 |
security: Vanta remediation pass 2026-10-07 (MCP SDK, sharp, hono) (#26260) | ||
|
|
0069c3b68e |
chore(template-starter-agent): default every model to gpt-6-luna (#26266)
## Summary The starter agent template registers the built-in `webSearchTool`, a placeholder that resolves to a **provider-executed** search tool supporting only OpenAI, Anthropic, Google, and xAI. With the template defaulting to `mastra/deepseek/deepseek-flash-latest` (#25989), every run threw `WEB_SEARCH_UNSUPPORTED_PROVIDER`. Rather than removing web search, this switches every model string in the template to `mastra/openai/gpt-6-luna`: - `agents/agent.ts`: agent model + observational memory model - `welcome.ts`: welcome generation model + doc comment ## Test plan - `gpt-6-luna` verified present in `packages/core/src/llm/model/capabilities/openai.json` - `npx tsc --noEmit` passes in the template - `grep` confirms no remaining deepseek model strings in the template <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 The starter agent now uses an OpenAI model instead of a DeepSeek model. This change aims to keep the template’s web search working with its default model. ## Changes - Changed the agent model and observational-memory model in `agents/agent.ts` to `mastra/openai/gpt-6-luna`. - Changed the welcome-message model and its documentation in `welcome.ts` to `mastra/openai/gpt-6-luna`. - Kept the existing welcome-message fallback behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
c4d6e92634 |
feat(template-connect-agent): adopt tools() + channels() (#25989)
## Summary
Updates `templates/template-connect-agent` to the current
`@mastra/connect` API surface:
- **`connect()` → `tools()`** — the template was on the deprecated
alias; the agent's toolset resolver and the activity-digest workflow now
use `tools()` directly.
- **`channels()` wired into the Mastra instance** — `channels: await
channels()` mounts the Slack/Discord/Telegram webhook + OAuth routes up
front, so connecting a channel on the platform brings it live without a
redeploy. No new template dependencies: the channel provider packages
ship as dependencies of `@mastra/connect`.
- **Deps track `latest`** — all `@mastra/*` deps and the `mastra` CLI
stay on the `latest` dist-tag; the stable releases
(`@mastra/connect@1.0.0`, `@mastra/core@1.75.0`, `mastra@1.33.0`)
include the current Connect API. The `legacy-peer-deps` `.npmrc`
workaround that was needed while tracking alpha is removed.
- README updated to match (channels section, `tools()` wording, channel
scoping under "Making it yours").
## Test plan
Verified against the published stable builds (`@mastra/connect@1.0.0`,
`@mastra/core@1.75.0`):
- `npm install` + `tsc --noEmit` clean
- `mastra build` succeeds (top-level `await channels()` bundles fine)
- Live boot with real platform credentials + Postgres:
- `/api/agents/connect-agent` resolves **768 integration tools**
- channel webhook routes answer: unknown webhook ids return the channel
handlers' JSON 404 (`{"error":"Unknown webhook"}`), distinct from Hono's
plain-text 404 on unmatched paths
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
|
||
|
|
bf0dd07091 |
security: Vanta remediation pass 2026-10-05 (#25966)
Update 2026-10-06 (commits added on this branch; origin/main merged in to clear the lockfile conflict) Dependabot opened new alerts overnight (4 critical). This pass adds: - braintrust ^3.24.0 -> ^3.36.0 in @mastra/braintrust. braintrust 3.27 pulled in simple-git 3.36.0, which has critical and high advisories (GHSA-x6jw-m9v5-85vh, GHSA-v5rq-49vh-5v5c via @simple-git/argv-parser 1.1.1, GHSA-858h-whjf-mvg5, GHSA-g4wm-2vf7-vfgr). Those are only fixed in simple-git 4. braintrust 3.36 no longer depends on simple-git, so simple-git drops out of the lockfile. @mastra/braintrust only uses initLogger and currentSpan. - wrangler ^4.110.0 -> ^4.147.0 (devDependency of @mastra/deployer-cloudflare, type-only import). This moves workerd 1.20260708.1 -> 1.20261001.1 on that chain (Aikido medium). workerd 1.20260714.1 is still there through the miniflare 4 devDependency in stores/cloudflare and stores/cloudflare-d1. - source-map-js 1.2.1 -> 1.2.2 (GHSA-68fv-2mgg-jv7q, high). Added the floor `source-map-js@>=1.0.0 <1.2.2: 1.2.2` in the root and in 15 nested pnpm workspaces (9 e2e projects, mastracode/web, otel-bridge agent-hub and hono-multi, agent-builder, mcp and memory integration-tests). postcss, css-tree, magicast and @tailwindcss/node all declare ^1.2.x. In the customer-refund template, a plain npm lock refresh was enough (no override). - postcss-selector-parser: raised the existing floor from `>=7.1.0 <7.1.3: 7.1.3` to `>=7.1.0 <7.1.6: 7.1.6` (GHSA-rj75-hqrm-r3gf, medium). - observability/_examples/otel-bridge/hono-multi: tsx catalog ^4.21.0 -> ^4.23.15. tsx 4.23 uses esbuild ~0.28, so esbuild 0.27.2 is gone (Aikido high and low, fixed in 0.28.1). - Changeset `.changeset/vanta-2026-10-06.md`: patch for @mastra/braintrust. Still not fixed (as of 2026-10-06) - sprintf-js 1.0.3/1.1.3 (GHSA-hp3w-g68c-fv3c): no patched release. - postcss-selector-parser 6.0.10/6.1.3: the fix is only in 7.1.6. @tailwindcss/typography 0.5.20 pins 6.0.10 exactly, and cssnano 6/postcss-calc 9 use ^6. - katex 0.16.47 (GHSA-238p-pmpm-9mq7, low): the fix is in 0.18.2. mermaid 12.1.0 still declares ^0.16.47. - http-cache-semantics: 4.3.0 is now older than 24h, but it still doesn't touch the max-stale path, and the advisory still lists no patched version. - braces 3.0.3 has no new release. - The rest of the deferred list below is unchanged. --- Vanta remediation for 2026-10-05. The finding list was rebuilt from GitHub Dependabot, OSV-scanner on every tracked lockfile, and Aikido intel (full intel.aikido.dev feed re-pulled today). It is not a Vanta export. What changed Package bumps - probe-image-size ^7.2.3 -> ^7.4.0 in @mastra/memory (GHSA-gjj5-9665-rwrc, high). - verdaccio ^6.10.4 -> ^6.10.5 in the 9 e2e projects. That moves @verdaccio/core to 8.3.2 and js-yaml 5.2.2 -> 5.4.1 (GHSA-r3ph-w7gj-g6xm, medium). - smol-toml 1.8.0 -> 1.9.0 pin in @mastra/code-sdk. Root lockfile refresh (no range changes) - serialize-javascript 7.0.5 -> 7.1.2, shell-quote 1.10.0 -> 1.12.0, ws 7.5.11 -> 7.5.13, enhanced-resolve -> 5.26.0, fs-extra 11.3.5 -> 11.4.1, @sinclair/typebox 0.27.8 -> 0.27.12, @zip.js/zip.js 2.8.26 -> 2.23.0, memfs/@jsonjoy.com/fs-snapshot 4.57.2 -> 4.80.0, @vue/* 3.5.38 -> 3.5.43. pnpm overrides, for parents that pin an exact vulnerable version. All stay in the same major. - modern-tar 0.7.7 (just-bash), smol-toml 1.9.0 (just-bash, @blaxel/core, @react-grab/cli, modal), strnum 2.4.2 (fast-xml-parser 5.10.1), inline-style-parser 0.2.9 (style-to-object 1.0.11), `@opentelemetry/configuration>yaml` 2.9.1 (sdk-node 0.221). Nested lockfiles - shell-quote floor raised from <1.10.0 to <1.11.0 in examples/agent, examples/voice-agent and otel-bridge/agent-hub. - yaml 2.9.0 -> 2.9.1 in e2e-tests/pkg-outputs, examples/durable-agents, mastracode/web, packages/mcp/integration-tests and the customer-refund template. - next 16.3.6 -> 16.3.8 in packages/memory/integration-tests. - customer-refund template: tinypool 2.1.0 -> 2.1.2 through an override scoped to oxfmt. oxfmt 0.59 pins it exactly, and bumping oxfmt would change the template's format check. Not fixed here - braces 3.0.3 (GHSA-vfj7-8cjw-p6xm) and http-cache-semantics 4.2.0 (GHSA-ch52-4w7c-c8xp): no patched release. http-cache-semantics 4.3.0 is outside the advisory range, but it doesn't change the max-stale code path, so bumping to it would only hide the alert. - extract-zip 2.0.1: no patched release. It comes from the webdriverio chain that #25855 removes. - workerd 1.20260708/1.20260714 (Aikido medium): miniflare 4.x stops at workerd 1.20260730. The fix needs miniflare 5, which is only published as an alpha. - Major-only: @ai-sdk/provider-utils 2.2.8 / ai 4.3.19 (AI SDK v4), @opentelemetry/core 1.30.1, esbuild 0.18/0.25/0.27.0 (convex pins 0.27.0 exactly), js-yaml 3, brace-expansion 1/2, uuid 11, zod 3, pino 8/9, undici 6, plus other Aikido lows. - websocket-driver 0.7.5: Aikido says the fix is 0.8.x, but no 0.8 is published on npm. The changeset is a patch for @mastra/memory and @mastra/code-sdk. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 This PR updates several dependencies that have security fixes. It also adds version rules so nested projects use safer versions of related packages. ## Changes - Updates `probe-image-size` in `@mastra/memory` to `^7.4.0` and pins `smol-toml` in `@mastra/code-sdk` to `1.9.0`. - Updates Verdaccio to `^6.10.5` in nine end-to-end test projects. - Raises `shell-quote` overrides to `1.11.0` and adds overrides for transitive dependencies, including `yaml`, `source-map-js`, `postcss-selector-parser`, `modern-tar`, `smol-toml`, `strnum`, `inline-style-parser`, and `tinypool`. - Updates `braintrust` to `^3.36.0`, `wrangler` to `^4.147.0`, and `tsx` to `^4.23.15`. - Adds patch changesets for `@mastra/memory`, `@mastra/code-sdk`, and `@mastra/braintrust`. The changesets report no API changes. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
4358322b7b |
chore(deps): override upstream-blocked vulnerable transitive deps (#25853) | ||
|
|
dd16328874 |
security: Vanta remediation pass 2026-10-02 (#25816) | ||
|
|
acb22d7557 |
security: Vanta remediation pass 2026-10-01 (#25694)
## Summary Daily Vanta vuln remediation for 2026-10-01 (inventory from GitHub Dependabot + OSV + Aikido lens; Vanta UI export unavailable this run). ### Bumps / floors - `nodemailer` `^9.0.1` → `^10.0.6` (e2e monorepo template) + matching test assertion - `fastify` `^5.12.4` → `^5.12.5` - `hono` `4.13.5` → `4.13.8` (`templates/template-security-incident-triage`) - `ajv` `8.17.1` → `8.18.0`, `fast-uri` `3.1.8` (`mastracode/sdk/scripts/acp-validator`) - `js-yaml` 5.x floor → `5.4.1` (root + `e2e-tests/experiment-worker`) - `dompurify` floor → `3.4.16` - `@ai-sdk/provider-utils` floors → `3.0.40` / `4.0.56` / `5.0.52` ### Deferred - **extract-zip@2.0.1** — no patched release (latest is 2.0.1) - **@ai-sdk/provider-utils@2.2.8** — AI SDK v4 pin; Aikido fix is major →4.x only - **webpack-dev-middleware@7.4.6** — pnpm supply-chain trust-downgrade blocks install (`ERR_PNPM_TRUST_DOWNGRADE`) - **uuid@3.4.0** and other major-only Aikido lows (es-module-lexer, raw-body, yargs, zod3, protobufjs7, @noble/hashes, nanoid3) Do not merge via agent. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 This PR updates several software packages to versions reported to fix security problems. It also records updates the author deferred because a suitable fix was unavailable or the upgrade was blocked or too large. ## Changes - Updated `nodemailer` in the e2e monorepo template to `^10.0.6` and changed the related test assertion. - Updated `fastify` to `^5.12.5` in the Fastify adapter and Inngest workflow. - Updated `hono` to `4.13.8` in the security incident triage template. - Updated `ajv` to `8.18.0` and added `fast-uri` `3.1.8` to the ACP validator. - Added `js-yaml` overrides for affected version ranges in the root workspace and experiment worker. - Raised workspace dependency floors for `dompurify` and `@ai-sdk/provider-utils`. - Added a patch changeset for `@mastra/core`. ## Deferred updates The author reports deferring `extract-zip@2.0.1` because no patched release was available, `@ai-sdk/provider-utils@2.2.8` because it requires a major upgrade from the pinned AI SDK v4, and `webpack-dev-middleware@7.4.6` because installation returned `ERR_PNPM_TRUST_DOWNGRADE`. The author also reports deferring `uuid@3.4.0` and other major-only Aikido findings: `es-module-lexer`, `raw-body`, `yargs`, `zod3`, `protobufjs7`, `@noble/hashes`, and `nanoid3`. ## Tests Test results were not provided. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
098d5036d5 |
fix(template-starter-agent): drop Redis dependency (#25706)
## Summary The starter template no longer wraps its agent in `createDurableAgent` (#25629), so the Redis-backed event cache that was there to replay chunks across client disconnects / restarts is dead weight. Postgres covers the data path on its own, and dropping Redis means one fewer service a user has to run locally to try the template. Changes: - Remove `@mastra/redis` and `ioredis` from `package.json` - Remove `RedisServerCache` wiring and the `cache` field from `src/mastra/index.ts` - Remove `REDIS_URL` from `.env.example` and the boot guard that threw when it was unset - Drop the Redis bullet from `README.md` get-started and the "streams survive restarts" bullet it enabled - Update `AGENTS.md` to list only `DATABASE_URL` as required - Update `package.json` description to not mention the Redis cache Postgres is still required. ## Test plan - `grep -rn -i 'redis\|REDIS_URL' templates/template-starter-agent/` returns nothing - Boot the template locally with `REDIS_URL` unset to confirm the server starts <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 The starter agent no longer needs Redis, so this change removes its Redis setup. Users still need PostgreSQL to run the starter. ## Changes - Removed `@mastra/redis`, `ioredis`, and `RedisServerCache` configuration. - Removed the `REDIS_URL` startup requirement and Redis instructions from the README, `.env.example`, and `AGENTS.md`. - Updated the package description to remove its Redis event-cache reference. - Removed the claim that streams survive client disconnects and process restarts. ## Testing The provided test plan checks for remaining Redis references and starts the template without `REDIS_URL`. The available summary does not report whether these checks were completed. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |