fix(deps): update dependency @mastra/libsql to v1

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@mastra/libsql (source)	^0.12.0 → ^1.0.0

---

Release Notes

mastra-ai/mastra (@​mastra/libsql)

v1.13.2

Compare Source

v1.13.0

Compare Source

Minor Changes

• Added LibSQL storage support for durable harness sessions. (#​17712)

  const storage = new LibSQLStore({ id: 'mastra-storage', url: 'file:./mastra.db' });
  
  const harness = new Harness({
    ownerId: 'my-app',
    agent,
    memory,
    storage,
    modes: [{ id: 'default', defaultModelId: '__GATEWAY_OPENAI_MODEL__' }],
    defaultModeId: 'default',
  });

• Add ThreadStateLibSQL, the LibSQL implementation of the new ThreadStateStorage domain. It persists per-thread, per-type state (e.g. the agent task list under type: "task") in the mastra_thread_state table, keyed by (threadId, type). Composing a LibSQL store wires this domain automatically, so an agent's task list now survives a process restart. (#​17820)

Patch Changes

• dependencies updates: (#​17148)

  • Updated dependency @libsql/client@^0.17.3 ↗︎ (from ^0.15.15, in dependencies)

• Fixed concurrent writes silently disappearing when using LibSQL with a local (file:) database. (#​16796)

  LibSQL backs a local database with a single connection. When one operation held an interactive write transaction (for example, persisting workflow snapshots) and another operation wrote at the same time (for example, creating a dataset experiment), the second write could be swept into the open transaction and rolled back — so it appeared to succeed but never persisted. This surfaced as concurrent agent/workflow runs losing unrelated records.

  Writes on a LibSQL client are now serialized, so a write issued during an in-flight transaction no longer interleaves with it.

• Updated dependencies [d468acb, 575f815, 34839c1, 053735a, 306909a, 5191af8, 43bd3d4, e6fa79e, 904bcdf, 7f5ee1d, 1e9aab5, 2bccba4, bf8eb6d, e9be4e7, 493a328, d53cfc2, 65799d4, c268c89, 34839c1, 014e00f, 029a414, d468acb, b147b29, d371ac1, 2bccba4, 0c72f03, cf182b7, 3b45ea9, a049c2a, f084be1, b147b29, 2a96528, f2ab060, 5d302c8, 34839c1, a952852, 2656d9c, 63e3fe1, 1d4ce8d, 8c68372]:

  • @​mastra/core@​1.42.0

v1.12.1

Compare Source

Patch Changes

• Added LibSQL support for the notifications storage domain so notification signals can persist thread-scoped inbox records. (#​17241)

  import { LibSQLStore } from '@​mastra/libsql';
  
  const storage = new LibSQLStore({ url: 'file:./mastra.db' });

• Fixed LibSQL memory cleanup so in-memory stores initialize their tables before clearing data. This prevents reset flows from failing with missing table errors such as mastra_resources. (#​17532)

• Updated dependencies [c973db4, 552285e, 77e686c, ece8dba, e751af2, e2a8380, be3f1cd, a34d9db]:

  • @​mastra/core@​1.39.0

v1.12.0

Compare Source

Minor Changes

• Added the tool_provider_connections storage domain. Stored agents can now persist per-agent ToolProvider config that round-trips on read/write/create. Runtime connection resolution (per-author, shared, caller-supplied) ships in a follow-up PR. (#​17247)

  What you can do

  • Pin a connection on a stored agent's config and have it round-trip on read/write/create.
  • Persist multiple connections per toolkit so a follow-up runtime PR can fan-out to the right one at execution time.

  Example

  import { LibSQLStore } from '@​mastra/libsql';
  
  const storage = new LibSQLStore({ url: process.env.DATABASE_URL });
  
  // Persist an OAuth connection that an agent can pin later
  await storage.toolProviders.upsertConnection({
    authorId: 'user-123',
    providerId: 'composio',
    connectionId: 'auth_abc',
    toolkit: 'gmail',
    label: 'Work inbox',
    scope: 'per-author',
  });
  
  // List a user's own connections (admin can omit authorId to list across users)
  const { items } = await storage.toolProviders.listConnectionsByAuthor({
    authorId: 'user-123',
    providerId: 'composio',
  });

  Additive — existing stored agents continue to work unchanged. The runtime that consumes this domain ships in a follow-up PR.

  PR 1 of 3 split from #​17224.

Patch Changes

• Added a public close() method to LibSQLStore that releases SQLite file handles and cleans up the WAL/shm sidecar files. Previously these handles stayed open until the process exited, which on Windows caused EBUSY errors when removing the storage directory after shutdown. Mastra.shutdown() now calls close() automatically, so you no longer need to reach into private fields. (#​17306)

  const storage = new LibSQLStore({ id: 'my-store', url: 'file:./dev.db' });
  
  // Release all file handles, including WAL/shm sidecar files
  await storage.close();
  
  // Now safe to remove the storage directory on all platforms, including Windows
  await fs.rm('./dev.db', { recursive: true, force: true });

• Updated dependencies [fa63872, d779de3, 1750c97, 9283971, f07b646, d8838ae, 40f9297, 19a8658, 850af77, 0f0d1ba, a18775a, 1baf2d1, 8c31bcd, 0e32507, 95b14cd, 07c3de7, 0bf2d93, 7b0d34c, a659a77, aa36be2, 3332be9, 212c635, d8838ae, 9aa5a73, f73c789, 8bd16da, c8630f8, 94dfef6, 47f71dc, 50ceae2, a122f79, 8cdde58, 3a081c1, 49f8abc, 847ff1e, 0c1ed1d, 259d409, 9e16c68, cefca33, d00e8c5, 36fa7e2, 87e9774, 65a72e7, fe9eacd, 4c02027, 0f77241, 849efb9, 92ff509, 3fce5e7, a763592, db79c86, 6855012, 80c7737, 7fef31c, 7fef31c, 3f1cf47]:

  • @​mastra/core@​1.38.0

v1.11.1

Compare Source

Patch Changes

• Fixed scheduler performance and correctness issues that could cause excessive Postgres CPU and noisy failed runs. (#​16805)

  • Added missing indexes on the schedules tables that the tick loop polls every 10 seconds: (status, next_fire_at) on mastra_schedules and (schedule_id, actual_fire_at) on mastra_schedule_triggers. Without these the scheduler performed a full sequential scan on every tick.
  • The scheduler tick loop is now only started when at least one workflow declares a schedule (or scheduler.enabled is set explicitly), so deployments without scheduled workflows no longer poll the database at all.
  • The scheduler now validates that a schedule's target workflow is still registered before firing it. Schedules whose target workflow has been removed from the Mastra config are skipped for a short grace window and then deleted, so stale rows stop producing failed workflow runs forever.
  • The scheduler is now lazily initialized inside startWorkers(). Accessing mastra.scheduler before startWorkers() runs throws a descriptive error instead of returning a half-initialized instance.

• Updated dependencies [452036a, c272d50, 27fd1b7, 5ba7253, 5556cc1, f73980d, 5499303, a702009, 9aee493, d8692af, 1a9cc60, 8cdb86c, 8534d79, eda90c5, a935b0a, 9c88701, c78f8cd, e146aad, ac79462, 1a0ec78, e47bca7, afc004f, 0031d0f, 841a222, 64c1e0b, 40d83a9, 4e88dc6, 19018f0, 19281c7, 3498b49, d52b6fe, 408be73, 359439b, 71a820b, 1698f5e]:

  • @​mastra/core@​1.36.0

v1.11.0

Compare Source

Minor Changes

• Added favorites support to storage adapters so callers can favorite/unfavorite stored agents and skills, query favorite state alongside list results, and filter listings by visibility. (#​16580)

  Example

  const storage = new LibSQLStore({
    /* config */
  });
  const favorites = await storage.getStore('favorites');
  
  await favorites?.favorite({
    userId: 'user-1',
    entityType: 'agent',
    entityId: 'agent-42',
  });

Patch Changes

• Bumped @mastra/core peer dependency floor to >=1.34.0-0 so the new @mastra/core/storage/domains/favorites subpath is available. Older @mastra/core versions don't ship the FavoritesStorage base class these adapters now extend. (#​16580)

• Fixed a workspace PATCH bug: omitted config fields in a PATCH no longer overwrite previously-persisted values with undefined. (#​16580)

• Updated dependencies [b661349, 816b974, 271c044, bad08e9, 816b974, b32ba5f, 75c7c38]:

  • @​mastra/core@​1.35.0

v1.10.1

Compare Source

Patch Changes

• Fixed Workflow run snapshots no longer lose fields when serialized for storage. The libsql safeStringify cycle-detection treated any object that appeared more than once in a snapshot as a circular reference and dropped it. Because snapshot.result and the final step's context[step].output share the same reference on success, snapshot.result was being silently stripped on every persist. This caused listWorkflowRuns to return runs with snapshot.result === undefined and broke workflow resume when suspended-state fields were shared elsewhere in the snapshot. (#​16368)

• Fixed Workflow runs no longer fail to persist when request context contains non-serializable values (for example functions, circular references, or platform proxy objects). This prevents errors when saving workflow snapshots and scorer results. See #​12301. (#​12573)

• Respect optional resourceId in getThreadById so scoped thread lookups return null when the thread belongs to a different resource. (#​14237)

  Example:

  const thread = await memory.getThreadById({
    threadId: 'my-thread-id',
    resourceId: 'my-user-id',
  });
  // Returns null if the thread does not belong to 'my-user-id'.

• Improved local LibSQL startup performance by applying conservative local SQLite performance settings before initialization, exposing local PRAGMA overrides, and reducing schema initialization contention. (#​16513)

• Track suspendedAt and suspendPayload on background tasks. SQL adapters auto-migrate the new columns via alterTable. (#​16260)

• Added LibSQL indexes for thread message history queries to speed up recent-message and observational-memory loading. (#​16513)

• Updated dependencies [9f17410, 7ad5585, ac47842, cc189cc, d1fdbd0, 210ea7a, 7c275a8, bae019e, 890b24c, f984b4d, 6742347, b59316f, 0f48ebf, 37c0dc5, 087e413, 83218c8, ef6b584, c6eb39e, 7b0ad1f, d91ebe2, 62666c3, 33f5061, 4af2160, 087e413, 265ec9f, ce01024, 6ce80bf, f984b4d, 136c959, 9268531, 13ead79, dccd8f1, 4df7cc7, f180e49, 9260e01, 2f6c54e, aca3121, e06a159, 4dd900d, b560d6f, 99869ec, 900d086, 4c0e286, 55f1e2d, 4ff5bdf, 9cdf38e, 087e413, db34bc6, 990851e, bbcd93c, 8373ff4, d48a705, 308bd07, 6068a6c, 36b3bbf, d86f031, b275631, 00106be, bd36d8e, 11c1528, 4999667, e2a079c, 8ac9141, 25184ff, 534a456, 105e454, aebde9c, 36bae07, 5688881]:

  • @​mastra/core@​1.33.0

v1.10.0

Compare Source

Minor Changes

• Extend the schedules storage schema to support owned schedules and richer trigger audit. This is a breaking schema change to mastra_schedules and mastra_schedule_triggers; scheduled workflows are still in alpha so no compat shim is provided. (#​16166)

  • Schedule gains optional ownerType / ownerId so a schedule row can be attributed to an owning subsystem (e.g. an agent that owns a heartbeat schedule). Workflow schedules leave both fields unset.
  • ScheduleTrigger.status is renamed to outcome and the type is widened to ScheduleTriggerOutcome so future outcome values can be added without another rename.
  • ScheduleTrigger gains a stable id primary key and new triggerKind, parentTriggerId, and metadata fields. triggerKind distinguishes schedule-fire rows from later queue-drain rows (used by upcoming heartbeat work); parentTriggerId links related rows; metadata carries outcome-specific context.
  • The libsql, pg, and mongodb adapters all add the new columns/indexes. Their @mastra/core peer dependency is tightened to >=1.32.0-0 <2.0.0-0 so installing a new storage adapter against an older core (or vice-versa) surfaces a peer-dependency warning at install time instead of silently writing/reading the wrong field.
  • Scheduler producer, server schemas/handler, and client SDK types are updated to use the new fields. The triggers response on GET /api/schedules/:id/triggers now returns outcome instead of status.
  • The bundled Studio (Mastra CLI) is updated to read outcome so the schedule detail page keeps polling and rendering publish-failure rows correctly.

• Added the schedules storage domain so LibSQL-backed Mastra apps can use scheduled workflows. Creates mastra_schedules and mastra_schedule_triggers tables on init. (#​15830)

Patch Changes

• Updated dependencies [6dcd65f, 86c0298, c05c9a1, ca28c23, e24aacb, 7679a63, 7fce309, 1d64a76, 1c2dda8, c721164, 1b55954, 7997c2e, 5adc55e, 7679a63, a0d9b6d, e97ccb9, c5daf48, 70017d7, cd96779, b0c7022, e4942bc]:
  • @​mastra/core@​1.32.0

v1.9.1

Compare Source

Patch Changes

• Added platform channels framework with ChannelProvider interface, ChannelsStorage domain, and ChannelConnectResult discriminated union supporting OAuth, deep link, and immediate connection flows. Channels can be registered on the Mastra instance and expose connect/disconnect/list APIs for platform integrations. (#​15876)

• Updated dependencies [1723e09, 629f9e9, 25168fb, ab34b5a, 5fb6c2a, 2b0f355, 394f0cf, b2deb29, 66644be, e109607, 310b953, 3d7f709, 48a42f1, 8091c7c, 2c83efc, 43f0e1d, da0b9e2, 282a10c, 04151c7, 8091c7c]:

  • @​mastra/core@​1.31.0

v1.9.0

Compare Source

Minor Changes

• Use DiskANN vector_top_k() index for faster vector queries when available (#​14913)

  LibSQLVector.query() now automatically uses the existing DiskANN index for approximate nearest neighbor search instead of brute-force full table scans, providing 10-25x query speedups on larger datasets. Falls back to brute-force when no index exists.

Patch Changes

• Add BackgroundTasksStorage domain implementation so @mastra/core background task execution works with any storage adapter. (#​15307)

• Added getTraceLight method to the observability storage, returning only lightweight span fields needed for timeline rendering. This avoids transferring heavy fields like input, output, attributes, and metadata when they are not needed. (#​15574)

• Updated dependencies [20f59b8, aba393e, 3d83d06, e2687a7, fdd54cf, 6315317, a371ac5, 0474c2b, 0a5fa1d, 7e0e63e, ea43e64, f607106, 30456b6, 9d11a8c, 9d3b24b, 00d1b16, 47cee3e, 62919a6, d246696, 354f9ce, 16e34ca, 7020c06, 8786a61, 9467ea8, 7338d94, c80dc16, af8a57e, d63ffdb, 47cee3e, 1bd5104, e9837b5, 8f1b280, 92dcf02, 0fd90a2, 8fb2405, 12df98c]:

  • @​mastra/core@​1.26.0

v1.8.1

Compare Source

Patch Changes

• Fixed "column does not exist" errors when using experiment review features on databases created before the review pipeline was introduced. Startup now automatically migrates older experiment tables to the latest schema. (#​15304)

• Added entityVersionId, parentEntityVersionId, and rootEntityVersionId columns to observability storage tables (spans, metrics, scores, feedback, logs) for filtering and grouping traces by entity version. Added ALTER TABLE migrations for existing databases. Added targetType, targetId, agentVersion, and status filters to listExperiments, and traceId and status filters to listExperimentResults. (#​15317)

• Updated dependencies [87df955, 8fad147, 582644c, cbdf3e1, 8fe46d3, 18c67db, 4ba3bb1, 5d84914, 8dcc77e, aa67fc5, fd2f314, fa8140b, 190f452, e80fead, 0287b64, 7e7bf60, 184907d, 075e91a, 0c4cd13, b16a753]:

  • @​mastra/core@​1.25.0

v1.8.0

Compare Source

Minor Changes

• Implemented updateObservationalMemoryConfig() in Postgres, LibSQL, and MongoDB storage adapters. This enables per-record config overrides for observational memory thresholds, supporting the new memory.updateObservationalMemoryConfig() API in @mastra/memory. (#​15115)

Patch Changes

• Updated dependencies [f32b9e1, 7d6f521, a50d220, 665477b, 4cc2755, ac7baf6, ed425d7, 1371703, 0df8321, 98f8a8b, ba6f7e9, 7eb2596, 1805ddc, fff91cf, 61109b3, 33f1ead]:
  • @​mastra/core@​1.23.0

v1.7.4

Compare Source

Patch Changes

• Added expectedTrajectory support to dataset items across all storage backends and API layer. Dataset items can now store trajectory expectations that define expected agent execution steps, ordering, and constraints for trajectory-based evaluation scoring. (#​14902)

• Updated dependencies [cb15509, 81e4259, 951b8a1, 80c5668, 3d478c1, 2b4ea10, a0544f0, 6039f17, 06b928d, 6a8d984, c8c86aa]:

  • @​mastra/core@​1.22.0

v1.7.3

Compare Source

Patch Changes

• The internal architecture of observational memory has been refactored. The public API and behavior remain unchanged. (#​14453)

• Add getReviewSummary() to experiments storage for aggregating review status counts (#​14649)

  Query experiment results grouped by experiment ID, returning counts of needs-review, reviewed, and complete items in a single query instead of fetching all results client-side.

  const summary = await storage.experiments.getReviewSummary();
  // [{ experimentId: 'exp-1', needsReview: 3, reviewed: 5, complete: 2, total: 10 }, ...]

• Added scorerIds persistence for datasets. The scorerIds field is now stored and retrieved correctly when creating or updating datasets. (#​14783)

• Updated dependencies [dc514a8, e333b77, dc9fc19, 60a224d, [fbf22a7](https://redirect.github.com/m

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.