chore(deps): bump @opentelemetry/sdk-node and @mastra/core in /03-integrations/agentic-frameworks/typescript_mastra

[dependabot]

Removes @opentelemetry/sdk-node. It's no longer used after updating ancestor dependency @mastra/core. These dependencies need to be updated together.

Removes @opentelemetry/sdk-node

Updates @mastra/core from 0.24.0 to 1.32.1

Release notes

Sourced from @​mastra/core's releases.

May 4, 2026

Highlights

Fine-Grained Authorization (FGA) across Mastra (core + server adapters + MCP)

Mastra now supports relationship-based, resource-level authorization with centralized enforcement before agent runs (generate()/stream()), tool/workflow execution, and memory thread access via new IFGAProvider/IFGAManager + checkFGA()/FGADeniedError. FGA is also enforced consistently in @mastra/server handlers, all built-in server adapters (Express/Fastify/Hono/Koa), and MCP tool execution.

WorkOS-backed FGA provider (@mastra/auth-workos)

New MastraFGAWorkos implements IFGAManager on top of the WorkOS Authorization API, including check/require/filterAccessible, resource CRUD, role assignments, org scoping, JWT/bearer-token context handling, and permission/resource mappings for multi-tenant setups.

Scheduled Workflows (cron-native) + scheduler + full HTTP/Studio/client support

Workflows can now declare schedule in createWorkflow() to run on cron with automatic promotion to the evented engine, type-checked inputData/initialState/requestContext, and safe multi-instance claiming (CAS) via WorkflowScheduler. End-to-end support includes new schedules storage domains/adapters (PG/LibSQL/MongoDB + in-memory for tests), new @mastra/server routes + @mastra/client-js schedule methods, and new Studio UI for listing schedules, viewing trigger history, and durable pause/resume.

MCP Apps: interactive UI resources over MCP (SEP-1865) + resource listing/reading APIs

MCP servers can now publish ui:// HTML app resources via appResources, with new listResources()/readResource() on MCPServerBase and client/server endpoints (MastraClient.getMcpServerResources() / readMcpServerResource(), plus @mastra/server routes). @mastra/mcp adds proxy helpers (MCPClientServerProxy, toMCPServerProxies()) and stamps serverId into tool metadata to support multi-server UI resolution.

Observability upgrades: nested-run querying + bounded high-cardinality metrics + Datadog bridge

New listBranches/getBranch (plus getSpans and getStructure) let you find and fetch runs even when an entity only appears as a nested span (not root traces), with corresponding HTTP endpoints and store implementations (ClickHouse/DuckDB). Metrics now support count_distinct plus server-side TopK (limit, ordering) for fast dashboards on high-cardinality fields; ClickHouse also adds skip indexes to speed drilldowns, and a new DatadogBridge keeps auto-instrumented spans correctly nested under Mastra spans.

Breaking Changes

• Schedules storage schema changed (mastra_schedules, mastra_schedule_triggers): adds ownerType/ownerId, renames ScheduleTrigger.status → outcome, adds trigger id PK plus triggerKind/parentTriggerId/metadata; GET /api/schedules/:id/triggers now returns outcome instead of status (no compat shim; scheduled workflows are alpha).
• @mastra/client-js Vector return types changed to match runtime:
  • vector.getIndexes() → string[] (was { indexes: string[] })
  • vector.upsert() → { ids: string[] } (was string[])
  • vector.query() → QueryResult[] (was { results: QueryResult[] })

Changelog

@​mastra/core@1.32.0

Minor Changes

• Added Fine-Grained Authorization (FGA) support for relationship-based, resource-level access control. FGA answers "can this user perform this action on this specific resource?" — enabling multi-tenant isolation and per-resource permissions. (#15410)

  New interfaces: IFGAProvider (read-only checks) and IFGAManager (read + write operations) with types for access checks, resources, and role assignments.

  Enforcement at all execution points: FGA checks are automatically enforced before agent execution (generate(), stream()), tool execution, workflow execution, and memory thread access. When no FGA provider is configured, all checks are skipped (backward compatible).

  New utility: checkFGA() provides centralized FGA enforcement with FGADeniedError for denied checks. MastraMemory.checkThreadFGA() adds thread-level access control.

  Request-aware authorization: Resource ID resolvers receive request context so route-level FGA checks can derive tenant- or request-scoped resource IDs.

  Typed permission constants: Strongly-typed permission identifiers (e.g. 'agents:execute', 'workflows:execute', 'memory:threads:read') for use in authorization config and permissionMapping.

  const mastra = new Mastra({
    server: {
      fga: new MastraFGAWorkos({ apiKey, clientId }),
    },
  });

... (truncated)

Commits

• 9a5a9b8 chore: version - exit prerelease mode
• a6e9417 chore: version packages (alpha) (#16192)
• cc0469d refactor(core): consolidate fetch retry helper (#16155)
• d5445f5 chore: version - exit prerelease mode
• b474594 chore: version packages (alpha) (#16182)
• b0c7022 fix(harness): use type 'image' and mimeType for image parts in convertToHarne...
• a0d9b6d fix(core): check for failed steps in buildResumedBlockResult before a… (#14410)
• 7679a63 feat: add MCP Apps extension support (SEP-1865) (#16004)
• ea686fc chore: regenerate providers and docs [skip ci]
• 1d64a76 fix(memory): inherit custom gateway config in Observational Memory agents (#1...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​mastra/core since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

Latest scan for commit: 999b33f | Updated: 2026-05-11 16:53:22 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-05-11T16:43:41+00:00
• ASH version: 3.0.0

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

• Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
• Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
• High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
• Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
• Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
• Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

• Time: Duration taken by each scanner to complete its analysis
• Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

• PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
• FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
• MISSING: Scanner could not run because required dependencies/tools are not installed or available
• SKIPPED: Scanner was intentionally disabled or excluded from this scan
• ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

• CRITICAL: Only Critical severity findings cause scanner to fail
• HIGH: High and Critical severity findings cause scanner to fail
• MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
• LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
• ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

• (g) = global: Set in the global_settings section of ASH configuration
• (c) = config: Set in the individual scanner configuration section
• (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

• All statistics are calculated from the final aggregated SARIF report
• Suppressed findings are counted separately and do not contribute to actionable findings
• Scanner status is determined by comparing actionable findings to the threshold

Scanner	S	C	H	M	L	I	Time	Action	Result	Thresh
bandit	0	0	0	0	0	0	567ms	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	31.4s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	320ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	6.3s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	955ms	0	PASSED	MED (g)
grype	0	5	0	4	2	0	42.7s	9	FAILED	MED (g)
npm-audit	0	0	0	0	0	0	1.0s	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	0	0	0	3.1s	0	PASSED	MED (g)

Detailed Findings

Show 9 actionable findings

Finding 1: GHSA-37qj-frw5-hhjh-fast-xml-parser

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-37qj-frw5-hhjh-fast-xml-parser
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A high vulnerability in npm package: fast-xml-parser, version 5.2.5 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 2: GHSA-j3q9-mxjg-w52f-path-to-regexp

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-j3q9-mxjg-w52f-path-to-regexp
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A high vulnerability in npm package: path-to-regexp, version 8.3.0 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 3: GHSA-6rw7-vpxm-498p-qs

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-6rw7-vpxm-498p-qs
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A medium vulnerability in npm package: qs, version 6.14.0 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 4: GHSA-27v5-c462-wpq7-path-to-regexp

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-27v5-c462-wpq7-path-to-regexp
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A medium vulnerability in npm package: path-to-regexp, version 8.3.0 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 5: GHSA-jp2q-39xq-3w4g-fast-xml-parser

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-jp2q-39xq-3w4g-fast-xml-parser
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A medium vulnerability in npm package: fast-xml-parser, version 5.2.5 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 6: GHSA-jmr7-xgp7-cmfj-fast-xml-parser

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-jmr7-xgp7-cmfj-fast-xml-parser
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A high vulnerability in npm package: fast-xml-parser, version 5.2.5 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 7: GHSA-8gc5-j5rx-235r-fast-xml-parser

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-8gc5-j5rx-235r-fast-xml-parser
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A high vulnerability in npm package: fast-xml-parser, version 5.2.5 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 8: GHSA-m7jm-9gc2-mpf2-fast-xml-parser

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-m7jm-9gc2-mpf2-fast-xml-parser
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A critical vulnerability in npm package: fast-xml-parser, version 5.2.5 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Finding 9: GHSA-gh4j-gqv2-49f6-fast-xml-parser

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-gh4j-gqv2-49f6-fast-xml-parser
• Location: 03-integrations/agentic-frameworks/typescript_mastra/package-lock.json:1

Description:
A medium vulnerability in npm package: fast-xml-parser, version 5.2.5 was found at: /03-integrations/agentic-frameworks/typescript_mastra/package-lock.json

---

Report generated by Automated Security Helper (ASH) at 2026-05-11T16:43:34+00:00