Skip to content

build(deps): bump @mastra/cloudflare-d1 from 1.1.1 to 1.3.1 - #1108

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/mastra/cloudflare-d1-1.3.1
Open

build(deps): bump @mastra/cloudflare-d1 from 1.1.1 to 1.3.1#1108
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/mastra/cloudflare-d1-1.3.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor

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

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.1

Patch Changes

1.3.1-alpha.0

Patch Changes

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)

... (truncated)

Commits
  • 3cd96a3 chore: version - exit prerelease mode
  • 3086f23 chore: version packages (alpha) (#22241)
  • a58483c fix(core): preserve cancellation during background task dispatch (#22228)
  • 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)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [@mastra/cloudflare-d1](https://github.com/mastra-ai/mastra/tree/HEAD/stores/cloudflare-d1) from 1.1.1 to 1.3.1.
- [Release notes](https://github.com/mastra-ai/mastra/releases)
- [Changelog](https://github.com/mastra-ai/mastra/blob/main/stores/cloudflare-d1/CHANGELOG.md)
- [Commits](https://github.com/mastra-ai/mastra/commits/@mastra/cloudflare-d1@1.3.1/stores/cloudflare-d1)

---
updated-dependencies:
- dependency-name: "@mastra/cloudflare-d1"
  dependency-version: 1.3.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants