## Description
`@mastra/discord` pinned `@chat-adapter/discord` to `4.40.0` and
`@mastra/teams` used `~4.40.0`, while `@mastra/core` moved `chat` to
`^4.43.0`. Every `@chat-adapter/*` release depends on the exact `chat`
release with the same version, so an app with core plus either package
installs two copies of `chat`:
```sh
pnpm add @mastra/core@1.81.0 @mastra/discord@1.3.2 @mastra/teams zod@4
ls node_modules/.pnpm | grep '^chat@'
# chat@4.40.0_zod@4.6.7
# chat@4.44.0_zod@4.6.7
```
The discord pin was correct when it landed in #25002 (it matched core's
`chat` at the time). It went stale when #28417 bumped core, slack and
telegram but not discord or teams. Renovate didn't catch it because the
"Chat adapter" group only matched `chat` and `@chat-adapter/slack`.
This PR:
- moves `chat` and all four `@chat-adapter/*` packages into the pnpm
catalog at `^4.44.0`, and points core, `@mastra/factory` and the channel
packages at `catalog:`
- widens the Renovate "Chat adapter" group to `@chat-adapter/*`
- drops the "pinned to 4.40.0" wording from the discord README
Installing the packed core, discord and teams tarballs into a fresh app
now gives a single `chat@4.44.0`, and the repo lockfile has one `chat`
entry.
Tested locally: typecheck and tests for `@mastra/discord`,
`@mastra/slack`, `@mastra/teams`, `@mastra/telegram`, core
`src/channels`, the factory Slack integration, and core/factory
typecheck.
The two smaller requests in the issue (passing an adapter instance to
`DiscordProvider`, back-off in core's `startGatewayLoop`) are out of
scope here.
## Related issue(s)
Fixes#29283
## 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)
- [ ] 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
Mastra and its channel packages now use matching versions of the chat
software. This helps prevent apps from installing separate copies that
may not work together.
## Changes
- Added `chat` and the Discord, Slack, Teams, and Telegram adapters to
the pnpm catalog at `^4.44.0`.
- Updated core, factory, and all four channel packages to use catalog
versions.
- Expanded Renovate’s “Chat adapter” group to match every
`@chat-adapter/*` package and `chat`.
- Updated the Discord README to remove the adapter pin wording and
clarify the reaction retry behavior.
- Added changesets for patch releases of the affected packages.
## Validation
The author reports that packed core, Discord, and Teams packages install
one `chat@4.44.0` in a fresh app, and that the repository lockfile has
one `chat` entry. The author also reports passing typechecks and tests
for Discord, Slack, Teams, Telegram, core channels, and the factory
Slack integration.
Accepting an adapter instance in `DiscordProvider` and adding back-off
to core’s `startGatewayLoop` are out of scope.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## 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 -->
## Description
Adds an official `@mastra/parallel` integration package with typed
Mastra-native Search and Extract tools. It uses the official
`parallel-web` client directly and provides individual tool factories
plus `createParallelTools()`.
Includes mocked tests, documentation, package registration, an
integration icon, and a changeset. This does not change Mastra Code
routing or provider precedence.
### Validation
- `pnpm --filter @mastra/parallel test` (19 tests passed)
- `pnpm --filter @mastra/parallel build:lib`
- `pnpm --filter @mastra/parallel lint`
## Related issue(s)
Closes#22068
## 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 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
-->
## ELI5
This PR adds official Parallel tools for Mastra agents. Agents can now
search the web and extract content through Parallel with typed inputs,
clear results, and shared configuration.
## Changes
- Added the new `@mastra/parallel` integration package.
- Added:
- `createParallelSearchTool()`
- `createParallelExtractTool()`
- `createParallelTools()`
- `getParallelClient()`
- Added lazy client creation with API-key validation and
environment-variable support.
- Added input validation for URLs, countries, calendar dates, fetch
policies, and other API options.
- Normalized Parallel results, errors, usage data, and warnings.
- Added mocked tests for client behavior, tool creation, request
mapping, validation, response handling, and SDK errors.
- Added package documentation, sidebar registration, icon, Renovate
configuration, and a changeset.
- Kept Mastra Code routing and provider precedence unchanged.
## Validation
- 19 tests pass.
- Library build succeeds.
- Linting succeeds.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Renovate PR #19080 was failing because newer @opencode-ai/plugin
versions pull in effect@4.0.0-beta.83, which pnpm 11 rejects under the
workspace's trustPolicy: no-downgrade setting.
This pins @opencode-ai/plugin to 1.14.48 (which resolves
effect@4.0.0-beta.59, already trusted) and tells Renovate to skip plugin
updates until upstream ships a version that doesn't trigger the trust
downgrade. No new trust exceptions are added — the existing policy stays
strict.
```diff
- "@opencode-ai/plugin": "^1.2.27"
+ "@opencode-ai/plugin": "1.14.48"
```
The broader @opencode-ai/* Renovate group is untouched, so
@opencode-ai/sdk and other OpenCode packages continue to get minor/patch
updates normally.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This change keeps one tool version locked to a safe older release so
updates don’t break the project’s security/trust checks. It also tells
Renovate to stop trying to update that one package for now, while
leaving other package updates alone.
## Summary
- Pinned `@opencode-ai/plugin` in `integrations/opencode/package.json`
to `1.14.48`.
- Added a Renovate `packageRules` entry to disable updates for
`@opencode-ai/plugin` until a compatible upstream release is available.
- Left the workspace trust policy unchanged and did not add any new
trust exceptions.
- Regenerated the lockfile only to reflect the specifier change.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: Mastra Code (alibaba-token-plan/glm-5.2) <noreply@mastra.ai>
This tightens up Renovate grouping so related dependency updates land
together instead of as scattered PRs.
It adds groups for a few shared ecosystems like MCP, browser automation,
Composio, OpenCode, React Hook Form, Smithy, Tailwind, WorkOS, and
workspace providers. It also fixes vector DB package names and expands
existing database, schema, and Inngest groups.
Validated with `pnpm dlx --package renovate renovate-config-validator
renovate.json`.
No changeset because this only changes repo automation config.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
Renovate is the bot that updates your dependencies. This change tells it
to collect “similar” updates together (by ecosystem) so it opens fewer,
more organized upgrade pull requests instead of many small ones.
## Technical Details
**What changed in `renovate.json`:**
- **Expanded existing dependency grouping rules:**
- **Database clients**: added additional TypeScript DB type packages
(e.g., `@types/pg`, `@types/mssql`).
- **Schema tools**: widened the match list to include more Zod /
JSON-schema conversion helpers (e.g., `zod-from-json-schema*`,
`zod-to-ts`, `json-schema-to-zod` variants).
- **Inngest**: broadened matches to include the `@inngest/*` scoped
packages.
- **Added new dependency groups** so Renovate consolidates related
updates:
- **Browser automation**, **Chat adapter**, **Composio**, **MCP (Model
Context Protocol)**, **OpenCode**, **React Hook Form**, **Smithy**.
- **Refined other grouping rules:**
- **Tailwind ecosystem**, **WorkOS**, and **Workspace providers** were
updated/expanded (including additional `@vercel/sandbox`-ending provider
matches in the visible section).
- **Vector database package naming** was adjusted so the grouping
matches the correct package names.
- Some prior rule placement for groups like **Vector Databases** and
**Workflow Platforms** was reorganized within the `packageRules` array.
- **Validation:** ran `renovate-config-validator` via `pnpm dlx
--package renovate renovate-config-validator renovate.json` to confirm
the config is valid.
- **No changeset added** because this is a repository automation
configuration change.
Lines changed in `renovate.json`: **+95 / -8**.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Mastra Code (openai/gpt-5.5) <noreply@mastra.ai>
## Summary
- disable major Renovate AI SDK updates across the monorepo and tests
- keep minor and patch AI SDK updates enabled for non-example packages
- leave examples unaffected so majors can still be considered there if
desired
## Testing
- jq empty renovate.json
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## ELI5
This PR tells Renovate to stop automatically applying big (major)
updates for the Vercel AI SDK across the main repo and tests, while
still allowing smaller fixes and minor updates; example projects are
left able to receive major AI SDK updates.
## Changes
- renovate.json
- Enabled OSV vulnerability alerts: "osvVulnerabilityAlerts": true.
- Added/Enabled lock file maintenance: "lockFileMaintenance" enabled
with schedule "before 6am on monday" and "automerge": true.
- Confirmed global schedule: ["before 6am on monday"].
- Added packageRules targeting the Vercel AI SDK (matchSourceUrls:
"https://github.com/vercel/ai") in package.json files, excluding
examples/** and docs/**:
- "AI SDK" (applies to package.json excluding examples/** and docs/**):
disabled major updates (matchUpdateTypes: ["major"], enabled: false).
- "AI SDK" (same scope): allow minor and patch updates
(matchUpdateTypes: ["minor", "patch"], enabled).
- "AI SDK Examples" (applies to examples/**/package.json): no
update-type restriction so examples remain eligible for major updates.
- Ensured examples/docs remain excluded from the "disable major" rule
via matchFileNames/matchPaths patterns.
## Rationale
- Prevent automated major AI SDK bumps in the main codebase and tests so
they can be reviewed manually, while continuing automated minor/patch
updates and allowing examples to experiment with major upgrades.
## Testing
- Ran: jq empty renovate.json.
Lines changed: +23/-0
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Mastra Code (openai/gpt-5.4) <noreply@mastra.ai>
Adds the `group:monorepos` preset to automatically group updates from
the same monorepo into a single PR. This covers 28+ monorepos used in
the project including babel, nextjs, playwright, vitest, tailwindcss,
tanstack, radix-ui, opentelemetry, aws-sdk, and others.
https://claude.ai/code/session_01GVqtxaeyULfBMH9yve5stt
## Description
<!-- Provide a brief description of the changes in this PR -->
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
Fixes#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
Co-authored-by: Claude <noreply@anthropic.com>
## Description
This PR updates the Renovate configuration to improve dependency update
management:
1. **Expanded `ignorePaths`**: Added `templates/**`, `**/examples/**`,
and `**/_examples/**` to the ignore list to prevent Renovate from
creating PRs for dependencies in template and example directories.
2. **Removed examples-specific rule**: Deleted the dedicated `examples`
package rule that was previously handling updates for `examples/**`
files with a Monday schedule and patch/minor-only restrictions. This is
now superseded by the broader ignore path configuration.
These changes simplify the Renovate configuration while ensuring that
example and template code doesn't trigger unnecessary dependency
updates, reducing noise in the PR workflow.
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, if applicable -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [x] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [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
https://claude.ai/code/session_01Crsj158CigGFQsWCQopKtu
Co-authored-by: Claude <noreply@anthropic.com>
## Description
<!-- Provide a brief description of the changes in this PR -->
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have performed a self-review of my own code
- [ ] 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
- [ ] New and existing unit tests pass locally with my changes
- [ ] I have generated a changeset for this PR
This PR expands workflow snapshot storage API so users can query
workflow runs, and filter on workflowname, time, and paginate.
- Added to current storage providers with tests
- Added deployer route
- Added function to workflow.ts
The Renovate config in this repository needs migrating. Typically this
is because one or more configuration options you are using have been
renamed.
You don't need to merge this PR right away, because Renovate will
continue to migrate these fields internally each time it runs. But later
some of these fields may be fully deprecated and the migrations removed.
So it's a good idea to merge this migration PR soon.
🔕 **Ignore**: Close this PR and you won't be reminded about config
migration again, but one day your current config may no longer be valid.
❓ Got questions? Does something look wrong to you? Please don't hesitate
to [request help
here](https://redirect.github.com/renovatebot/renovate/discussions).
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/mastra-ai/mastra).
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>