Mastra 1.61.0 makes concurrent workflow resume safe with an atomic claim and HTTP 409

GitHub (mastra-ai/mastra)·medium signalXBlueskyLinkedInCopy link

@mastra/core 1.61.0, released 24 August, fixes a duplicate-execution hazard: concurrent `resume()` calls now atomically claim a suspended run, losers get `WORKFLOW_RESUME_ALREADY_CLAIMED` and HTTP 409, and workflow state updates carry an `expectedStatus` guard. The release also adds caller-driven experiments so an external orchestrator such as Temporal workers can own the eval loop while Mastra stays the system of record, via `createExperiment`, `runExperimentItem`, `submitExperimentResult` and `finalizeExperiment` with upsert semantics on (experimentId, itemId, attempt). Generated servers gain configurable graceful shutdown with a `drainTimeout` and an option to disable Mastra's built-in signal handlers.