what stackpulse tracks
Mastra releases from GitHub
StackPulse watches Mastra release notes and keeps the original source link close to every summary.
#stacks/mastra/ai
Mastra release notes, breaking changes, and upgrade notes.
TypeScript agent framework with workflows, RAG, and evals StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
releases
7
breaking
2
security
0
deprecated
2
migrations
2
upgrade risk
Breaking changes and deprecations
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Source-backed next steps
Migration steps and recommended actions are only shown when the upstream release notes support them.
# latest_releases
source-backed@mastra/core@1.46.0highbreakingdeprecationmigrationfeatureJun 24, 2026
June 24, 2026
This release introduces multi-session architecture with isolated session management, HTTP harness operations, and cross-process signal delivery. It also adds deterministic agent experiments and new integrations.
affected
Users of Harness singleton and direct API calls will need to migrate to session-based operations.
action
Update code to use the new session-based APIs for state, events, and run control.
release_signals
-Harness no longer exposes a singleton harness.session; must use harness.createSession()
-Run control moved from Harness to Session (e.g., sendMessage, abort)
-Event subscription moved to session.subscribe()
-Thread lifecycle APIs moved to session.thread
-Model/mode switching moved to session.model.switch() and session.mode.switch()
!Removed deprecated Harness.getState() Harness.setState() compatibility wrappers
!Removed Harness.getObserverModelId, getReflectorModelId, and related methods
!Removed Harness.sendMessage, Harness.sendSignal, and related run-control methods
!Removed Harness.subscribe()
+Multi-session Harness architecture with isolated session management
+HTTP harness operations and remote session control via JS client
+Cross-process signal delivery with distributed leasing
+Deterministic agent experiments with tool mocks and multi-tenant datasets
+New integrations for Next.js, TanStack Start, and Archil filesystem provider
migration_steps5 steps
- 01Use harness.createSession() and operate on the returned Session
- 02Use session.state.get() session.state.set() instead of Harness state methods
- 03Access observational-memory via session.om
- 04Run control operations now on Session (e.g., session.sendMessage)
- 05Subscribe to events via session.subscribe()
@mastra/core@1.45.0mediumfeatureJun 19, 2026
June 19, 2026
This release brings performance improvements for long thread resumption, fixes for agent signal handling, and clearer system guidance for state signals. The WorkOS OAuth login issue has also been resolved.
affected
Users of long threads or agent signal handling will see performance and reliability improvements, while WorkOS OAuth users will have restored login functionality.
action
Update to the latest version to benefit from performance improvements and bug fixes.
release_signals
+Faster long-thread resume via improved state signal restoration
+More reliable signal turn handling in agents
+Clearer system guidance around automatic state signals
+Redesigned Studio panel & code-surface UI primitives in @mastra/playground-ui
+WorkOS OAuth login fix (PKCE verifier cookie missing)
@mastra/core@1.42.0highbreakingfeatureJun 12, 2026
June 12, 2026
This release introduces trusted system actor execution for workflows, tools, and agents, enabling server-side/background work without JWT/human membership requirements. It also adds a new SignalProvider framework for declarative agent signal wiring and makes task tools agent-agnostic with durable thread state storage.
affected
Developers using Harness APIs for question handling and plan approval will need to migrate to the new tool suspension APIs.
action
Update code to use `respondToToolSuspension` and handle `tool_suspended` events instead of deprecated question and plan approval APIs.
release_signals
-Removed `harness.respondToQuestion(...)` → use `harness.respondToToolSuspension(...)`
-Removed `ask_question` event → listen for `tool_suspended` and read `event.suspendPayload`
-Removed Harness question-related APIs/types (`registerQuestion`, `pendingQuestion`, `HarnessQuestion*` types)
-Removed `harness.respondToPlanApproval(...)` and `plan_approval_required/plan_approved` events → resume `submit_plan` via `respondToToolSuspension`
+Trusted system actor execution for workflows, tools, memory, and agents
+SignalProvider framework for declarative agent signal wiring (webhooks/polling/subscriptions)
+Agent-agnostic interactive tools via native tool suspension (ask_user, submit_plan)
+ThreadState storage domain for durable, agent-agnostic task tools
+New infrastructure/storage options: Postgres vNext observability, ClickHouse replication, durable harness sessions
@mastra/core@1.41.0highdeprecationmigrationfeatureJun 5, 2026
June 4, 2026
This release introduces per-request workspace sandboxes for multi-tenant deployments, enabling isolated working directories and permissions. It also adds `sandboxCacheKey` for background process continuity and unifies stream behavior with the `untilIdle` option.
affected
Developers using multi-tenant deployments or background processes are most affected by these changes.
action
Update code to use the new `untilIdle` option and `sandboxCacheKey` for background process continuity.
release_signals
!Deprecated `streamUntilIdle()` and `resumeStreamUntilIdle()` methods in favor of `stream(..., { untilIdle: true })` and `resumeStream(..., { untilIdle: true })`.
!Deprecated `/stream-until-idle` and `/resume-stream-until-idle` endpoints.
+Workspace `sandbox` now accepts a resolver function for per-request sandboxes.
+Added `sandboxCacheKey` for background process continuity across follow-up requests.
+Unified `untilIdle` option for `stream()` and `resumeStream()` methods.
+Stable placeholder instructions for resolver-backed sandboxes.
+Opt-in `instructions.dynamicSandbox` mode for per-request instructions.
migration_steps2 steps
- 01Replace `streamUntilIdle()` and `resumeStreamUntilIdle()` with `stream(..., { untilIdle: true })` and `resumeStream(..., { untilIdle: true })`.
- 02Use `sandboxCacheKey` for background process continuity across follow-up requests.
@mastra/core@1.40.0mediumfeatureJun 5, 2026
June 3, 2026
This release introduces support for routing embeddings through the Gateway using `mastra/provider/model` identifiers, enabling more flexible embedding model management.
affected
Developers using embedding models with Mastra Gateway are affected.
action
Update to `@mastra/core@1.40.0` to utilize the new Gateway embedding routing feature.
release_signals
+Added support for Gateway embedding routing with `mastra/provider/model` IDs.
@mastra/core@1.39.0highfeatureJun 4, 2026
June 3, 2026
This release introduces experimental thread-scoped notification signals with persisted inbox storage, processor state signals for memory-backed thread context, and type-safe message rendering with `@mastra/react`. It also adds support for notification inbox persistence across multiple storage backends and delivers working memory as state signals.
affected
Developers using Mastra for notification handling, thread state management, and message rendering will benefit from these new features.
action
Review the new `MessageFactory` component and consider adopting thread-scoped notification signals and processor state signals for improved functionality.
release_signals
+Thread-scoped notification signals with `agent.sendNotificationSignal()` and priority-aware delivery.
+Notification inbox persistence across Postgres, MongoDB, and LibSQL backends.
+Processor state signals for memory-backed thread context with `computeStateSignal()` and `agent.sendStateSignal()`.
+Working memory delivered as state signals with `workingMemory.useStateSignals`.
+Type-safe `MessageFactory` component in `@mastra/react` for per-part rendering.
@mastra/core@1.38.0highfeatureJun 3, 2026
June 2, 2026
This release introduces OAuth ToolProviders runtime, a new MySQL storage adapter, cloud sandbox options, experimental Code Mode for agents, and message-first thread APIs. It also includes enhancements for tool approvals and agent overrides.
affected
Users leveraging agents, tool approvals, and storage backends will benefit from new features and enhancements.
action
Review the new features and update your implementations to leverage the new capabilities.
release_signals
+OAuth ToolProviders runtime for stored agents with connection management
+New MySQL storage adapter with broad domain coverage
+Cloud sandbox and browser deployment options (Vercel MicroVM + Firecrawl Browser)
+Experimental Code Mode for TypeScript orchestration of agents
+Message-first and approval-first thread APIs for higher-level flows