docs(js): Move Mastra under integrations - #19045
Open
matejminar wants to merge 2 commits into
Open
Conversation
Group the Mastra exporter with the other AI stack integrations and update internal links to its new location. Preserve current and legacy page and Markdown export URLs with direct redirects that avoid redirect chains.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Remove the inherited explicit sidebar order so Mastra follows the integrations section's alphabetical ordering.
matejminar
marked this pull request as ready for review
August 13, 2026 14:46
Comment on lines
+2277
to
+2287
| { | ||
| source: '/platforms/javascript/guides/:guide/agent-tracing/mastra.md', | ||
| destination: | ||
| '/platforms/javascript/guides/:guide/configuration/integrations/mastra.md', | ||
| }, | ||
| { | ||
| source: | ||
| '/platforms/javascript/guides/:guide/agent-tracing/mastra/:path*', | ||
| destination: | ||
| '/platforms/javascript/guides/:guide/configuration/integrations/mastra/:path*', | ||
| }, |
Contributor
There was a problem hiding this comment.
Bug: The new redirects for Mastra documentation do not handle the canonical URL with a trailing slash, /agent-tracing/mastra/, which will cause a 404 error.
Severity: MEDIUM
Suggested Fix
Add a new redirect rule to specifically handle the canonical URL with a trailing slash. For example: { source: '/platforms/javascript/agent-tracing/mastra/', destination: '/platforms/javascript/configuration/integrations/mastra/' }.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: redirects.js#L2272-L2287
Potential issue: The new redirect rules for the moved Mastra documentation page are
incomplete. While they handle paths like `/agent-tracing/mastra.md` and sub-paths like
`/agent-tracing/mastra/:path*`, they fail to redirect the canonical URL
`/platforms/javascript/agent-tracing/mastra/` (with a trailing slash). The `:path*`
wildcard pattern does not match an empty segment following a path separator.
Consequently, users accessing the old canonical URL via bookmarks or search engine
results will encounter a 404 error instead of being redirected to the new location at
`/platforms/javascript/configuration/integrations/mastra/`.
Also affects:
redirects.js:2227~2247redirects.js:2248~2268
Did we get this right? 👍 / 👎 to inform future reviews.
shellmayr
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now, Mastra lives right under Agent Tracing making it look like it's the only thing we support.
This PR moves the Mastra exporter guide from Agent Tracing into the JavaScript integrations section, alongside Vercel AI, OpenAI, Anthropic, and the other supported AI stacks. The Agent Tracing overview now includes Mastra in its AI stack list, and existing internal links point directly to the new location.
Permanent redirects preserve the current and older Mastra page URLs, including framework-specific and Markdown export paths. Legacy URLs resolve directly to the new page without redirect chains.
Likely reason for why Mastra stood standalone is that it's technically exporter, not integration, but it's less confusing this way.