unstale

npm / @mastra/dynamodb

@mastra/dynamodb

What changed in @mastra/dynamodb 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.

1 breaking1 behavior and defaults1 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.8 on npm

@mastra/dynamodb 13 changes

Breaking changes 1

  • DynamoDB stores reject writes from durable agent executions that lost their run to crash recovery, preventing them from overwriting recovered messages, threads, or workflow state. Claims use the existing table; storage.prune() does not remove them yet. Requires @mastra/core 1.76.0 or…

    1.4.2release notes

Behavior and default changes 1

  • storage.prune() now deletes durable agent run fencing records. Configure retention.workflows.runOwnership by inactivity and retention.memory.runFences by time since retirement; fences for running executions are never pruned.

    1.4.3release notes

Fixes and other changes 1

  • Workflow step results can be recorded in the same write as workflow state, allowing evented workflows to resume with the correct state after a restart.

    1.4.1release notes