mirror of
https://github.com/mastra-ai/mastra.git
synced 2026-11-17 08:44:46 +00:00
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases ## @mastra/factory@0.29.0-alpha.6 ### Minor Changes - Added personal custom providers. A custom OpenAI-compatible endpoint is now saved either for yourself or for your organization, the same way provider API keys are. ([#29879](https://github.com/mastra-ai/mastra/pull/29879)) - **Personal endpoints** are visible only to you and are used by your personal sessions. - **Organization endpoints** are used by work that runs on the organization's credentials. Adding, editing or removing one now requires an organization admin. - Custom endpoints are added from the **Add provider** dialog and listed with the other providers. The separate "Custom providers" section is gone. - Editing an endpoint without retyping its API key keeps the saved key, as long as the URL stays on the same host. Moving it to another host asks for the key again. - Adding an endpoint under a name that is already in use is refused instead of replacing the existing one. So are names reserved for a built-in provider, its sign-in, or the Mastra Gateway (for example "OpenAI", "OpenAI Codex" or "Mastra Gateway"). - A Factory hosted on the Mastra platform only calls custom endpoints at a public HTTPS address. Saving one on plain HTTP, `localhost`, a private network or the cloud metadata address is refused with a message explaining why. Local and self-hosted Factories can still use endpoints on their own machine or network, such as Ollama or vLLM. **Before you upgrade** - Organization endpoints no longer apply to personal sessions. Add the endpoint again as a personal one to keep using it there. - On a hosted Factory, endpoints saved earlier on a local or plain-HTTP address are marked "URL not allowed" and their models are no longer offered. Edit them to a public HTTPS address. - Review your organization's endpoints. One named like a built-in provider (for example "OpenAI") still takes over that provider's models; remove it or rename it. The custom provider routes take a `scope` (`user` by default, or `org`). Saving with `previousId` edits that provider; saving without it adds one: ```http POST /web/config/custom-providers { "name": "My gateway", "url": "https://llm.example.com/v1", "models": ["my-model"], "scope": "org" } DELETE /web/config/custom-providers/my-gateway?scope=org ``` - Work Intake: what you select is what comes in. ([#30625](https://github.com/mastra-ai/mastra/pull/30625)) - **One list per service, no sync switches.** Settings → Work Intake lists each connected service with its selected sources and an Add account button. A service with nothing selected brings in nothing. Dependabot alerts keep their own switch. - **GitHub issues follow the list.** New GitHub issues become cards only for repositories in the GitHub list. Pull requests still come from every linked repository. On upgrade, every repository already linked to a Factory is added to the list once, so nothing stops arriving. Linking a repository adds it to the list unless the request sends `selectIntake: false`, and adding a repository to the list brings in its open issues. To link a repository without bringing in its issues: ```http POST /web/factory/projects/:projectId/source-control-connections/:connectionId/repositories { "repository": { "externalId": "99", "slug": "acme/app" }, "selectIntake": false } ``` - **Vanta follows its selection.** Vulnerabilities sync only while the Vanta source is selected. Organizations whose Vanta sync was on with nothing selected get the source selected once on upgrade. - **Routing has its own page.** The intake order and the Not routed list moved from Settings to Routing in board settings. - Fixed Factory server memory growing with every session it ever opened. Factory now unloads a session from server memory when it stops the session's sandbox (a card leaving a phase's context or finishing), and after 30 minutes without activity. Sessions that are running, waiting on an approval or answer, open in a browser tab, or running a background process in their sandbox stay loaded. Unloading keeps the thread, its messages, the session row and the sandbox, and the session's next message, run, wake or opened tab loads it again. Without `auth`, a deferred wake for an unloaded session waits until something else loads it, as it does after a restart. ([#30612](https://github.com/mastra-ai/mastra/pull/30612)) Change the timeout with `idleSessionUnload`, or pass `false` to keep every session loaded: ```ts const factory = new MastraFactory({ storage, idleSessionUnload: { idleMs: 60 * 60_000, sweepIntervalMs: 5 * 60_000 }, }); ``` - Asking a Factory session to work on a card now goes through the board, the way the board's own buttons do. Before, asking a Slack or web session to "review" a pull request that already had a card often ended in a side session posting its review in the chat, while the card's own review waited for approval. ([#30628](https://github.com/mastra-ai/mastra/pull/30628)) - `factory_transition_work_item` takes `rerun: true` to run the stage a card is already in again, as the board's **Start** button does. The run counts as approved by the person asking, and a busy card is refused as on the board. A rerun needs a person in the turn. Without `rerun`, a request for the card's own stage changes nothing and says whether its run is waiting for approval. The result now includes the card's `url`. - Asking for a side session still starts one. The tools now steer a plain "review this pull request" to the pull request's card, and keep side sessions for what people ask to run in one and for work no stage does, such as pushing fixes to a pull request. - Every tool that takes a work item also accepts the issue or pull request it tracks: its link, `owner/repo#12`, `group/project!7`, or a tracker key such as `ENG-42`. With several repositories linked, the link finds the right card where a bare `#12` might not. `factory_list_work_items` takes the same references as its query. - `factory_inspect_work_item` lists the card's stage, whether it can run again, and the stages its board lets it move to next. - `factory_start_session` only starts side sessions. Its `workItem` and `role` inputs are removed: they started a card's role without the board's rules, such as which stage the card is in and whether it is busy. ### Patch Changes - Added `GET /web/factory/projects/:id/work-items/:workItemId/session-repository`. It returns the repository a session on the card starts in, resolved with the same rules as the card's runs, or the reason the card has none. ([#30609](https://github.com/mastra-ai/mastra/pull/30609)) - Fixed reopened pull request review sessions loading the pull request's AGENTS.md and CLAUDE.md as trusted instructions. After a review card finished and the server restarted or unloaded the session, a new message in that session read instruction files from the pull request branch. Sessions that ever ran pull request or review work now keep reading instructions from the base branch, or read none when the trusted branch can't be determined. ([#30612](https://github.com/mastra-ai/mastra/pull/30612)) - **Settings › Tools** can now list each Mastra Connect connection's tools. The new `GET /web/integrations/platform/connect-tools/tools` route resolves the tools a session started by the signed-in user would get: Factory's default Connect tools, or what the `tools` option returns. It marks tools that ask for approval and lists the default tools Factory leaves out because they delete or archive. When the tools can't be resolved, it answers 502 `tools_unavailable` with the reason. ([#30610](https://github.com/mastra-ai/mastra/pull/30610)) - Fixed **Settings › Tools** saying Mastra Connect tools are off when a Factory sets the `tools` option, even when that option uses Connect tools (#30579). The page now lists the Platform project's connections whenever the Factory has Platform credentials and `MASTRA_PROJECT_ID`, and says that session tools come from code. When either one is missing, the page names it instead of listing every possible cause. ([#30607](https://github.com/mastra-ai/mastra/pull/30607)) - Reduced the work the Factory server does to keep the session sidebar and board up to date, and fixed session latency timestamps on LibSQL. ([#30648](https://github.com/mastra-ai/mastra/pull/30648)) - Projects without a linked repository no longer rebuild their session list on every sidebar poll. - Session activity now sorts only the cards that are running, waiting or held by a session, instead of every card on the board. - A session's first materialize, first message and first command times are now recorded once when several Factory processes share one LibSQL database, so a later write no longer replaces the first recorded time. - Fixed slow reading of the pull request number from GitHub card keys that contain very long runs of digits. The number returned is unchanged. ([#30577](https://github.com/mastra-ai/mastra/pull/30577)) - New, renamed and hidden sessions now show up in teammates' sidebars right away, instead of after up to a minute, and the sidebar no longer polls while a session starts. The `session-rows` and `session-activity` answers no longer include `settling`: every change to either answer now sends a frame on the project's feed. ([#30617](https://github.com/mastra-ai/mastra/pull/30617)) - Fixed deleting an intake rule being slow on remote databases and breaking other open rule edits. A delete now removes only the deleted rule instead of rewriting every rule after it, so the remaining rules keep their order and revision and edits opened before the delete still save. ([#30613](https://github.com/mastra-ai/mastra/pull/30613)) - Approving a held Factory run with `factory_resolve_proposal`, or retrying a failed one with `factory_retry_decision`, now makes the session follow the run's card, as moving the card already did. Before, a Slack session that approved a card's review could promise to post the result and then never hear how the review ended. Both results now include the card's `url`. ([#30637](https://github.com/mastra-ai/mastra/pull/30637)) - Fixed board cards showing a different session status than the sidebar. A card with a suggested run and a running session now shows it waits on you on the board too, and a card with one working and one starting session shows it working. ([#30624](https://github.com/mastra-ai/mastra/pull/30624)) - Fixed Factory starting a card's session in a repository the card doesn't come from. When a card's repository wasn't linked to the Factory, the draft started the session in the first linked repository and wrote that repository onto the card. The draft now asks the server which repository the card's session uses, and when there is none it shows why, for example "Repository acme/docs is not linked to this Factory.", starts nothing, and links to repository settings. When the lookup itself fails, the draft offers Retry. ([#30609](https://github.com/mastra-ai/mastra/pull/30609)) A card from GitHub in a Factory whose repositories are all on GitLab, or the reverse, is now refused the same way instead of starting in that Factory's repository, even when a repository there has the same name. - Improved sidebar performance in projects with many sessions. The Factory now builds the session list once and reuses it for everyone until a session, card or follow changes, so each sidebar request uses about a third of the server CPU it did. ([#30616](https://github.com/mastra-ai/mastra/pull/30616)) - Fixed the session status in Factory's sidebar and board. A person's own session now shows "Waiting on you" while its agent waits for their answer, instead of "Working". A session now shows "Working" while it runs on a thread opened after its first one, such as a new thread or a Slack conversation. A session shows "Initializing" only while a run waits on its first setup, so a session whose setup never finished, or that never ran, no longer stays stuck on "Initializing". ([#30627](https://github.com/mastra-ai/mastra/pull/30627)) - Updated dependencies [[`944bb3a`](944bb3ab0f), [`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`b1ba914`](b1ba914ea1), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/code-sdk@1.19.1-alpha.6 - @mastra/core@1.84.0-alpha.5 - @mastra/connect@1.4.1-alpha.2 ## create-factory@0.5.0-alpha.5 ### Minor Changes - Added a `--tag <dist-tag>` option to `create-factory`. It pins the scaffolded template's `mastra` and `@mastra/*` dependencies to the exact versions published under that npm dist-tag, so you can try a new Factory on prerelease packages: ([#30598](https://github.com/mastra-ai/mastra/pull/30598)) ```sh npx create-factory@latest my-factory --tag alpha ``` When the pinned versions include prereleases and the project uses npm, `create-factory` also writes `legacy-peer-deps=true` to the project's `.npmrc`, because npm otherwise rejects the prerelease peer ranges. ### Patch Changes - `create-factory --tag` now stops before installing when the npm registry lookup for a Mastra package fails, instead of keeping that package's template version and producing a project that mixes release channels. A package that simply has no release under the tag still keeps its template version with a warning. ([#30614](https://github.com/mastra-ai/mastra/pull/30614)) - Updated dependencies [[`c638825`](c638825c83), [`a6dbd29`](a6dbd29a4e), [`3c7c003`](3c7c00383d), [`b90d0ec`](b90d0ecd41), [`e22c5a7`](e22c5a7035)]: - mastra@1.40.0-alpha.5 ## @mastra/core@1.84.0-alpha.5 ### Minor Changes - Added `knowledge.movePage()` to move a page, with its child pages, to a new parent or scope from your app. The page keeps its ID, notes, pins and embeddings, and links by path follow it, so a sync that sees a page move at its source no longer has to remove and re-create it. ([#30631](https://github.com/mastra-ai/mastra/pull/30631)) ```ts await knowledge.movePage({ scope: 'docs:acme', path: 'inbox/plan', parent: 'projects/q4' }); ``` Links by name now stay correct when a page moves or a new page takes a name. A page moved to another scope, and every page under it, re-resolves its `[[Name]]` links in the new scope. A link that pointed at one page by name stops resolving once a second page answers to that name. When more than 99 pages share that name, the write logs a warning and `knowledge.reindexLinks()` repairs the rest. - Added `knowledge.reembed()` to embed Knowledge pages and notes that already exist, such as content written before `vector` and `embedder` were configured or after switching embedders. It runs in batches with a resumable cursor, doesn't change the pages, lists failures and pages over the chunk cap, and stops early with a cursor when the embedder keeps rate limiting. ([#30603](https://github.com/mastra-ai/mastra/pull/30603)) ```ts let cursor: string | undefined; do { const result = await knowledge.reembed({ scope: 'org:acme', cursor }); if (result.rateLimited) await new Promise(resolve => setTimeout(resolve, 60_000)); cursor = result.nextCursor; } while (cursor); ``` ### Patch Changes - Fixed slow handling of Gateway base URLs and Supabase URLs that contain very long runs of `/`. The resulting URLs are unchanged. ([#30577](https://github.com/mastra-ai/mastra/pull/30577)) - Fixed `run.restart()` running a step again when the workflow run finished or suspended after `restart()` read it but before `restart()` took it over from the process running it. Restarting a run that finished now returns its stored result, and restarting a run that suspended fails with the usual "This workflow run was not active" error. ([#30399](https://github.com/mastra-ai/mastra/pull/30399)) - Fixed workflow `.sleep()` and `.sleepUntil()` waits longer than about 24.8 days ending almost immediately. The next step now runs only after the full wait, on the default and evented engines. ([#30395](https://github.com/mastra-ai/mastra/pull/30395)) ## @mastra/auth-supabase@1.2.1-alpha.0 ### Patch Changes - Fixed slow handling of Gateway base URLs and Supabase URLs that contain very long runs of `/`. The resulting URLs are unchanged. ([#30577](https://github.com/mastra-ai/mastra/pull/30577)) ## @mastra/client-js@1.60.1-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 ## @mastra/react@1.15.1-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/client-js@1.60.1-alpha.5 ## @mastra/deployer-cloud@1.84.0-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/deployer@1.84.0-alpha.5 ## @mastra/longmemeval@1.1.43-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/libsql@1.31.0-alpha.2 ## @mastra/opencode@0.1.43-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/libsql@1.31.0-alpha.2 ## @mastra/code-sdk@1.19.1-alpha.6 ### Patch Changes - Fixed custom OpenAI-compatible providers so they only ever authenticate with the API key saved on the provider itself. ([#29879](https://github.com/mastra-ai/mastra/pull/29879)) - A custom provider is no longer given the saved credential of another provider when their names match (for example a custom provider called "OpenAI"). - A Mastra Gateway model (`mastra/...`) never runs on a custom provider that shares its id, with or without a gateway key. - Requests to a custom provider no longer follow redirects, so its API key is never sent on to another address. - A custom provider without an API key now works when sign-in is enabled, instead of failing with a missing credential error. If a custom provider in `settings.json` has no `apiKey` and relied on a key you saved for the provider it is named after (for example with `/api-keys`), set `apiKey` on the custom provider itself. - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34), [`464810d`](464810dcf8)]: - @mastra/core@1.84.0-alpha.5 - @mastra/pg@1.37.0-alpha.3 - @mastra/client-js@1.60.1-alpha.5 - @mastra/libsql@1.31.0-alpha.2 ## mastracode@0.50.1-alpha.6 ### Patch Changes - Added an ESM-only `mastracode/run-tui` export so a launcher can start the Mastra Code TUI with extra session options, such as Knowledge and its scopes: ([#30371](https://github.com/mastra-ai/mastra/pull/30371)) ```ts import { runTui } from 'mastracode/run-tui'; await runTui({ createMastraCode: { knowledge: { key: 'team', instance: knowledge }, scopes: ['org:acme'] } }); ``` Options given here replace the values Mastra Code would pass for the same keys, and apply to the interactive local TUI only. The `mastracode` command behaves as before. - Updated dependencies [[`944bb3a`](944bb3ab0f), [`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34), [`464810d`](464810dcf8)]: - @mastra/code-sdk@1.19.1-alpha.6 - @mastra/core@1.84.0-alpha.5 - @mastra/pg@1.37.0-alpha.3 - @mastra/libsql@1.31.0-alpha.2 ## @mastra/arize@1.3.31-alpha.1 ### Patch Changes - Raised the minimum versions of the OpenTelemetry SDK and OTLP exporter dependencies (`@opentelemetry/sdk-trace-base` and `@opentelemetry/core` `^2.12.1`, OTLP exporters `^0.223.1`) so they no longer resolve to releases that pin `@opentelemetry/resources` 2.12.0, which is affected by security advisory GHSA-qrww-3xmv-qhgm. If your project also depends on OpenTelemetry packages directly, check that they resolve `@opentelemetry/resources` 2.12.1 or later on the 2.x line, or 3.1.1 or later on the 3.x line. ([#30580](https://github.com/mastra-ai/mastra/pull/30580)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`93b823a`](93b823a847), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/otel-exporter@1.5.3-alpha.1 ## @mastra/arthur@0.4.31-alpha.1 ### Patch Changes - Raised the minimum versions of the OpenTelemetry SDK and OTLP exporter dependencies (`@opentelemetry/sdk-trace-base` and `@opentelemetry/core` `^2.12.1`, OTLP exporters `^0.223.1`) so they no longer resolve to releases that pin `@opentelemetry/resources` 2.12.0, which is affected by security advisory GHSA-qrww-3xmv-qhgm. If your project also depends on OpenTelemetry packages directly, check that they resolve `@opentelemetry/resources` 2.12.1 or later on the 2.x line, or 3.1.1 or later on the 3.x line. ([#30580](https://github.com/mastra-ai/mastra/pull/30580)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`93b823a`](93b823a847), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/otel-exporter@1.5.3-alpha.1 ## @mastra/laminar@1.3.33-alpha.1 ### Patch Changes - Raised the minimum versions of the OpenTelemetry SDK and OTLP exporter dependencies (`@opentelemetry/sdk-trace-base` and `@opentelemetry/core` `^2.12.1`, OTLP exporters `^0.223.1`) so they no longer resolve to releases that pin `@opentelemetry/resources` 2.12.0, which is affected by security advisory GHSA-qrww-3xmv-qhgm. If your project also depends on OpenTelemetry packages directly, check that they resolve `@opentelemetry/resources` 2.12.1 or later on the 2.x line, or 3.1.1 or later on the 3.x line. ([#30580](https://github.com/mastra-ai/mastra/pull/30580)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 ## @mastra/langfuse@1.6.7-alpha.1 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`93b823a`](93b823a847), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/otel-exporter@1.5.3-alpha.1 ## @mastra/otel-bridge@1.5.23-alpha.1 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`93b823a`](93b823a847), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/otel-exporter@1.5.3-alpha.1 ## @mastra/otel-exporter@1.5.3-alpha.1 ### Patch Changes - Raised the minimum versions of the OpenTelemetry SDK and OTLP exporter dependencies (`@opentelemetry/sdk-trace-base` and `@opentelemetry/core` `^2.12.1`, OTLP exporters `^0.223.1`) so they no longer resolve to releases that pin `@opentelemetry/resources` 2.12.0, which is affected by security advisory GHSA-qrww-3xmv-qhgm. If your project also depends on OpenTelemetry packages directly, check that they resolve `@opentelemetry/resources` 2.12.1 or later on the 2.x line, or 3.1.1 or later on the 3.x line. ([#30580](https://github.com/mastra-ai/mastra/pull/30580)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 ## @mastra/sentry@1.2.33-alpha.1 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`93b823a`](93b823a847), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/otel-exporter@1.5.3-alpha.1 ## mastra@1.40.0-alpha.5 ### Patch Changes - The Factory **Settings › Tools** page shows how many tools sessions get from each Mastra Connect connection. Expand one to see its tools with their descriptions, which ones ask for approval, and which ones Factory leaves out. With a `tools` option, a connection the code doesn't use shows no tools, and the code's other tools are listed under **Other tools from code**. ([#30610](https://github.com/mastra-ai/mastra/pull/30610)) - The Factory **Settings › Tools** page lists a project's Mastra Connect connections when the Factory sets its session tools in code, with a note that the `tools` option decides which of their tools sessions get. When Connect isn't set up, it names the missing Platform credentials or `MASTRA_PROJECT_ID` (#30579). ([#30607](https://github.com/mastra-ai/mastra/pull/30607)) - Added `mastra api factory work-item session-repository <project-id> <work-item-id>`. It shows the repository a session on a Factory card starts in, or why the card has none. ([#30609](https://github.com/mastra-ai/mastra/pull/30609)) - Fixed board cards showing a different session status than the sidebar. A card with a suggested run and a running session now shows it waits on you on the board too, and a card with one working and one starting session shows it working. ([#30624](https://github.com/mastra-ai/mastra/pull/30624)) - Fixed the session status in Factory's sidebar and board. A person's own session now shows "Waiting on you" while its agent waits for their answer, instead of "Working". A session now shows "Working" while it runs on a thread opened after its first one, such as a new thread or a Slack conversation. A session shows "Initializing" only while a run waits on its first setup, so a session whose setup never finished, or that never ran, no longer stays stuck on "Initializing". ([#30627](https://github.com/mastra-ai/mastra/pull/30627)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/deployer@1.84.0-alpha.5 ## @mastra/connect@1.4.1-alpha.2 ### Patch Changes - Fixed `posthog_run_query` failing provider-response validation whenever PostHog returned column types, which it does for every query with columns, even `select 1`. PostHog returns column types as `[columnName, clickhouseType]` pairs, such as `[["count()", "UInt64"]]`, and the tool now accepts them and returns them in that shape. The inferred type of `types` in the tool's output changes from `string[]` to `[string, string][]`, and a plain string entry, which PostHog never sends, is now rejected. Fixes [#30528](https://github.com/mastra-ai/mastra/issues/30528). ([#30541](https://github.com/mastra-ai/mastra/pull/30541)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 ## @mastra/deployer@1.84.0-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 ## @mastra/mcp-docs-server@1.3.14-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 ## @mastra/playground-ui@69.1.0-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/client-js@1.60.1-alpha.5 - @mastra/react@1.15.1-alpha.5 ## @mastra/server@1.84.0-alpha.5 ### Patch Changes - Reduced memory and CPU use when clients stream agent controller sessions. Each display-state update is now copied and serialized once and shared by every client of the session, instead of once per client, and the copy no longer duplicates message text or tool results. Display state is now serialized the same way as other stream events, so the bytes change for three kinds of value: an object with a `toJSON` method is sent as that method's result, an error keeps its own enumerable fields such as `statusCode`, and a value that cannot be cloned, such as a function, is left out and no longer closes the stream. ([#30615](https://github.com/mastra-ai/mastra/pull/30615)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 ## @mastra/elysia@0.1.24-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 ## @mastra/express@1.5.28-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 ## @mastra/fastify@1.5.28-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 ## @mastra/hono@1.7.26-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 ## @mastra/koa@1.7.28-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 ## @mastra/nestjs@0.3.1-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 ## @mastra/next@0.2.42-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 - @mastra/hono@1.7.26-alpha.5 ## @mastra/tanstack-start@0.2.42-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`0ed63d7`](0ed63d7308), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/server@1.84.0-alpha.5 - @mastra/hono@1.7.26-alpha.5 ## @mastra/pg@1.37.0-alpha.3 ### Patch Changes - Fixed `PgVector` calls failing with "Vector table ... does not exist" after an index was deleted with `deleteIndex()` and created again while that `PgVector` instance was still starting up. Also fixed `createIndex()` on that instance keeping the previous metric when the index was deleted and recreated, or rebuilt, during that time. ([#30578](https://github.com/mastra-ai/mastra/pull/30578)) - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 ## @mastra/temporal@0.6.1-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/deployer@1.84.0-alpha.5 ## create-mastra@1.40.0-alpha.5 ## @internal/playground@1.40.0-alpha.5 ### Patch Changes - Updated dependencies [[`7518c05`](7518c05d6f), [`b07dd23`](b07dd23713), [`33fba78`](33fba78931), [`e110fa6`](e110fa681a), [`d0a2fa4`](d0a2fa4e34)]: - @mastra/core@1.84.0-alpha.5 - @mastra/client-js@1.60.1-alpha.5 - @mastra/react@1.15.1-alpha.5 - @mastra/playground-ui@69.1.0-alpha.5 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
66 lines
1.6 KiB
66 lines
1.6 KiB