build(deps): bump @mastra/cloudflare-d1 from 1.1.1 to 1.3.0

[dependabot]

Bumps @mastra/cloudflare-d1 from 1.1.1 to 1.3.0.

Release notes

Sourced from @​mastra/cloudflare-d1's releases.

February 11, 2026

Highlights

Observational Memory Async Buffering (default-on) + New Streaming Events

Observational memory now buffers background observations/reflections by default to avoid blocking as conversations grow, and introduces structured streaming status/events (data-om-status plus buffering start/end/failed markers) for better UI/telemetry.

Workspace Mounts (CompositeFilesystem)

Workspaces can now mount multiple filesystem providers (S3/GCS/local/etc.) into a single unified directory tree via CompositeFilesystem, so agents and tools can access files across backends through one path structure.

Changelog

@​mastra/core@1.3.0

Minor Changes

• Added mount support to workspaces, so you can combine multiple storage providers (S3, GCS, local disk, etc.) under a single directory tree. This lets agents access files from different sources through one unified filesystem. (#12851)

  Why: Previously a workspace could only use one filesystem. With mounts, you can organize files from different providers under different paths — for example, S3 data at /data and GCS models at /models — without agents needing to know which provider backs each path.

  What's new:

  • Added CompositeFilesystem for combining multiple filesystems under one tree
  • Added descriptive error types for sandbox and mount failures (e.g., SandboxTimeoutError, MountError)
  • Improved MastraFilesystem and MastraSandbox base classes with safer concurrent lifecycle handling

  import { Workspace, CompositeFilesystem } from "@mastra/core/workspace";
  // Mount multiple filesystems under one tree
  const composite = new CompositeFilesystem({
  mounts: {
  "/data": s3Filesystem,
  "/models": gcsFilesystem
  }
  });
  const workspace = new Workspace({
  filesystem: composite,
  sandbox: e2bSandbox
  });

Stored agent fields (tools, model, workflows, agents, memory, scorers, inputProcessors, outputProcessors, defaultOptions) can now be configured as conditional variants with rule groups that evaluate against request context at runtime. All matching variants accumulate — arrays are concatenated and objects are shallow-merged — so agents dynamically compose their configuration based on the incoming request context.

New requestContextSchema field

Stored agents now accept an optional requestContextSchema (JSON Schema) that is converted to a Zod schema and passed to the Agent constructor, enabling request context validation.

... (truncated)

Changelog

Sourced from @​mastra/cloudflare-d1's changelog.

1.3.0

Minor Changes

• Memory list reads now surface database errors instead of silently returning empty results. (#17910)

  Previously, the paginated memory reads (listThreads, listMessages, listMessagesByResourceId, and listMessagesById) caught backend failures, logged them, and returned an empty payload like { threads: [], total: 0, hasMore: false }. A transient outage (locked table, dropped connection) was therefore indistinguishable from a genuinely empty result, so an agent reading conversation history during a brief failure would treat it as "no history" and could overwrite real state. These methods now re-throw the failure as a MastraError. Validation (USER) errors and genuinely empty results are unchanged.

  Behavior change

  Callers that previously received an empty result on a backend failure will now receive a thrown MastraError. If you call these read methods directly (rather than through an agent, which already surfaces errors), wrap them so a transient outage doesn't crash the caller:

  try {
    const { threads } = await storage.listThreads({ resourceId });
    // ...use threads
  } catch (error) {
    // a real backend failure. Decide whether to retry, surface, or degrade.
    // An empty thread list no longer hides here; it only means "no threads".
  }

Patch Changes

• Fixed a crash where updating a thread without a title (for example during observational memory buffering) could write a null title and violate the database's not-null constraint when running a newer @​mastra/memory against an older storage package. Memory now checks whether the connected storage adapter supports partial thread updates and backfills the existing title for older adapters, so mixed-version deployments keep working. See #21041 for the original title-clobbering fix this makes backward compatible. (#21257)

• Storage adapters now declare support for partial thread updates, letting newer @​mastra/memory preserve existing thread titles instead of overwriting them, while remaining safe against older versions. (#21257)

• Fixed resource-scoped message includes across storage adapters so included context cannot cross resource boundaries. (#20984)

• Fixed generated thread titles being clobbered during a turn (#21041)

  updateThread required both title and metadata, so callers that only needed to change metadata (message persistence, working memory, observational memory, channel subscriptions) had to read the thread and pass its title back. When title generation finished between that read and the write, the freshly generated title was overwritten with the stale one.

  title and metadata are now independently optional: omitting one leaves that column untouched. Callers that only change metadata no longer send a title, and message persistence no longer rewrites a thread row it just read.

• Updated dependencies [e7109ee, b8ce7ec, 2e4624e, 45a9147, a3a3624, 6246914, 6445eba, 86b7b77, 1c75e32, 296dc9a, f59032a, cdd5c33, 3f73c07, 772c0c8, d7cf7fa, 7c1ebb1, 0f9a448, 578bf2e, c47165c, 289f4ce, df31eb0, 9571e3a, 4f16ff8, b4c89b4, e6534fa, 210cb7a, 06b2d87, 1c67d85, ac01d63, 80a3324, e44e8f3, d9d2881, a810a05, ba24be6, 842b5fe, 990611b, 80bdf3a, c967a5e, dc4a25d, 9ba1247, fd96298, 66bbfb5, dc4a25d, f8da216, 4a09a9c, 5f798b3, 6a84954, 1e83a47, 52d8ef0, cdd5c33, 7fdcaa6, d6c56f9, e08e789, bf936e2, 7fb580a, ed5d606, f53d5bd, 32980a3, 01a2943, 82e3365, 6104347, 35cc901, a8b4cf0, 9571e3a, 333785c, bda2235, efd5c81, 1b482c2, 45bfb88, ff28284, 4bcdfaf, e3b9307, d6834c5, f33264f, 689f2c4, fcd0667, cfd0d9e, acc3513, 1670533, a7eb4a1, 0976933, 242b945, c52d346, af4636a, 01a2943, 2eabc09, 0023e79, c2ad51e, 25ca73d, 2f9ef3f, e7eefcb, fea5cae, 4d7aca2, e1cead1, 01a2943, d9d93b2, c4ec889, 4b59f78, eeae63e, 3dc97ea, 94e7ae9, e6a2860, 7010c5d, bab06b1, 3d01cd3, 7bf3086, 4c186a0, b0fa077, 0282e16, a8dd139, 6a667b4, 9be8878, e5786be, 2440e09, 2093fbd, a59049b, 7bd85ea, 83fa004, a463cdf, e7a5da4, 7b4393d, 0ea6b80]:

  • @​mastra/core@​1.58.0

1.3.0-alpha.3

Patch Changes

• Fixed a crash where updating a thread without a title (for example during observational memory buffering) could write a null title and violate the database's not-null constraint when running a newer @​mastra/memory against an older storage package. Memory now checks whether the connected storage adapter supports partial thread updates and backfills the existing title for older adapters, so mixed-version deployments keep working. See #21041 for the original title-clobbering fix this makes backward compatible. (#21257)

... (truncated)

Commits

• 387c6b7 chore: version - exit prerelease mode
• 7723ab9 chore: version packages (alpha) (#21274)
• dc4a25d fix(core): make partial thread updates backward compatible with older storage...
• 1dbd716 chore: version packages
• 4c186a0 fix(storage): stop thread title generation from being clobbered mid-turn (#21...
• aaf308a chore: version packages
• df31eb0 fix(storage): keep listMessages include inside the requested resource (#20984)
• 8e23a0b chore: version packages
• 8627c23 fix(stores): memory list reads throw on backend failure instead of returning ...
• 162f3da chore: version - exit prerelease mode
• Additional commits viewable in compare view

[dependabot]

Superseded by #1108.