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