Changelog

Summary

• Total packages with changes: 29
• Packages with major changes: 0
• Packages with minor changes: 1
• Packages with patch changes: 18

@mastra/agent-builder@1.0.0-beta.4

Patch Changes

• Fix install step validation error by making targetPath optional in InstallInputSchema. This resolves the "expected string, received undefined" error when running the agent builder template workflow without explicitly providing a targetPath parameter. (#10922)

Dependency Updates

• @mastra/core@1.0.0-beta.8
• @mastra/memory@1.0.0-beta.4

@mastra/ai-sdk@1.0.0-beta.6

Patch Changes

• Improve JSDoc comments (#10877)

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/braintrust@1.0.0-beta.4

Patch Changes

• Fix traceMap overwrite when multiple root spans share the same traceId (#10903)

  Previously, when multiple root spans shared the same traceId (e.g., multiple agent.stream calls in the same trace), the trace data would be overwritten instead of reused. This could cause spans to be orphaned or lost.

  Now both exporters check if a trace already exists before creating a new one, matching the behavior of the Langfuse and PostHog exporters.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/clickhouse@1.0.0-beta.4

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/client-js@1.0.0-beta.8

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/cloudflare@1.0.0-beta.5

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/cloudflare-d1@1.0.0-beta.4

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/convex@0.1.0-beta.2

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/core@1.0.0-beta.8

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

• setState is now async (#10944)

  • setState must now be awaited: await setState({ key: value })
  • State updates are merged automatically—no need to spread the previous state
  • State data is validated against the step's stateSchema when validateInputs is enabled (default: true)

• Add human-in-the-loop support for workflows used in agent (#10871)

@mastra/dane@1.0.0-beta.8

Dependency Updates

• @mastra/core@1.0.0-beta.8
• @mastra/upstash@1.0.0-beta.5
• @mastra/libsql@1.0.0-beta.5
• @mastra/memory@1.0.0-beta.4

@mastra/deployer@1.0.0-beta.8

Patch Changes

• Fix tsconfig.json parsing when file contains JSONC comments (#10952)

  The hasPaths() function now uses strip-json-comments to properly parse tsconfig.json files that contain comments. Previously, JSON.parse() would fail silently on JSONC comments, causing path aliases like @src/* to be incorrectly treated as npm scoped packages.

Dependency Updates

• @mastra/core@1.0.0-beta.8
• @mastra/server@1.0.0-beta.8

@mastra/deployer-cloud@1.0.0-beta.8

Dependency Updates

• @mastra/loggers@1.0.0-beta.3
• @mastra/core@1.0.0-beta.8
• @mastra/deployer@1.0.0-beta.8

@mastra/dynamodb@1.0.0-beta.4

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/express@0.0.2-beta.3

Dependency Updates

• @mastra/core@1.0.0-beta.8
• @mastra/server@1.0.0-beta.8

@mastra/hono@0.0.2-beta.3

Dependency Updates

• @mastra/core@1.0.0-beta.8
• @mastra/server@1.0.0-beta.8

@mastra/lance@1.0.0-beta.5

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/langsmith@1.0.0-beta.4

Patch Changes

• Fix traceMap overwrite when multiple root spans share the same traceId (#10903)

  Previously, when multiple root spans shared the same traceId (e.g., multiple agent.stream calls in the same trace), the trace data would be overwritten instead of reused. This could cause spans to be orphaned or lost.

  Now both exporters check if a trace already exists before creating a new one, matching the behavior of the Langfuse and PostHog exporters.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/libsql@1.0.0-beta.5

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/loggers@1.0.0-beta.3

Minor Changes

• Add redact option to PinoLogger for PII protection (#10919)

  Exposes Pino's native redact option in PinoLogger, allowing sensitive data to be automatically redacted from logs.

  import { PinoLogger } from '@mastra/loggers';
  
  const logger = new PinoLogger({
    name: 'MyApp',
    redact: {
      paths: ['*.password', '*.token', '*.apiKey', '*.email'],
      censor: '[REDACTED]',
    },
  });
  
  logger.info('User login', { username: 'john', password: 'secret123' });
  // Output: { username: "john", password: "[REDACTED]", msg: "User login" }

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/longmemeval@1.0.0-beta.8

Dependency Updates

• @mastra/core@1.0.0-beta.8
• @mastra/libsql@1.0.0-beta.5
• @mastra/memory@1.0.0-beta.4

@mastra/mcp-docs-server@1.0.0-beta.8

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/memory@1.0.0-beta.4

Patch Changes

• Fix connection pool exhaustion when saving many messages with semantic recall enabled. Instead of calling vector.upsert() for each message individually (which acquires a separate DB connection), all embeddings are now batched into a single upsert call. (#10954)

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/mongodb@1.0.0-beta.5

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/mssql@1.0.0-beta.5

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/pg@1.0.0-beta.5

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

• PostgresStore was setting this.stores = {} in the constructor and only populating it in the async init() method. This broke Memory because it checks storage.stores.memory synchronously in getInputProcessors() before init() is called. (#10943)

  The fix moves domain instance creation to the constructor. This is safe because pg-promise creates database connections lazily when queries are executed.

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/playground-ui@7.0.0-beta.8

Dependency Updates

• @mastra/core@1.0.0-beta.8
• @mastra/ai-sdk@1.0.0-beta.6
• @mastra/client-js@1.0.0-beta.8
• @mastra/react@0.1.0-beta.8

@mastra/react-hooks@0.1.0-beta.8

Dependency Updates

• @mastra/client-js@1.0.0-beta.8

@mastra/server@1.0.0-beta.8

Dependency Updates

• @mastra/core@1.0.0-beta.8

@mastra/upstash@1.0.0-beta.5

Patch Changes

• Fix saveScore not persisting ID correctly, breaking getScoreById retrieval (#10915)

  What Changed

  • saveScore now correctly returns scores that can be retrieved with getScoreById
  • Validation errors now include contextual information (scorer, entity, trace details) for easier debugging

  Impact
  Previously, calling getScoreById after saveScore would return null because the generated ID wasn't persisted to the database. This is now fixed across all store implementations, ensuring consistent behavior and data integrity.

Dependency Updates

• @mastra/core@1.0.0-beta.8