Add Mesa as a workspace filesystem provider#18627
Open
warrenbhw wants to merge 5 commits into
Open
Conversation
🦋 Changeset detectedLatest commit: cd81649 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@warrenbhw is attempting to deploy a commit to the Mastra Team on Vercel. A member of the Team first needs to authorize it. |
github-actions
Bot
added
the
Documentation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughIntroduces the ChangesMesa Filesystem Provider
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related issues
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
PR triageThis PR needs to fix an existing issue. Please link an issue in the PR description, for example with Applied label: PRs without a linked issue will automatically close after 1 day(s) with the label. Changed test gateChanged Test Gate is pending. The |
![superagent-security[bot]](https://avatars.githubusercontent.com/in/3287076?s=60&v=4){kind=small}
|
Dependency limit exceeded — report not shown. This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report. Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard. Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@workspaces/mesa/README.md`:
- Around line 7-9: The install example in the README is incomplete because the
example usage imports from `@mastra/core` while the package only peers on it, so
update the install step shown in the README to include `@mastra/core` alongside
`@mastra/mesa`. Make sure the documentation near the initial setup example clearly
reflects the dependency requirement so users can copy the install command and
run the sample imports without missing-module errors.
In `@workspaces/mesa/src/filesystem/index.integration.test.ts`:
- Around line 207-210: The toMesaPath helper currently uses path.join on
normalized input, which allows path traversal to escape this.root for values
like ../sibling or /../sibling. Update toMesaPath to enforce sandbox containment
by resolving the candidate path against this.root, verifying the result stays
within the rooted test directory, and rejecting any escaped path before
returning it. Use the existing toMesaPath method in the filesystem test adapter
to centralize this validation so all read/write/delete operations remain
isolated.
- Around line 23-25: The module-level MESA_API_KEY guard in the integration test
file is aborting Vitest collection instead of skipping these tests. Move the
check out of top-level execution and gate the suite or individual tests in the
existing MesaFilesystem integration test setup so they register as skipped when
MESA_API_KEY is missing, using the test suite entrypoints in
index.integration.test.ts rather than throwing during import.
In `@workspaces/mesa/src/filesystem/index.ts`:
- Around line 63-67: normalizePath currently calls path.normalize before the
path is rooted, so relative inputs with .. can keep a leading parent segment.
Update normalizePath to anchor the input to "/" first and then normalize the
rooted value, preserving the existing handling for empty and "." inputs. This
change should be made in normalizePath so every caller gets a correctly
collapsed absolute path for parent-directory checks and write paths.
- Around line 447-453: The exists() helper in MesaFileSystem is swallowing every
failure and returning false, which makes non-missing errors look like “path
absent.” Update exists(inputPath) to only return false for genuine not-found
cases from this.filesystem.exists(normalizePath(inputPath)), and rethrow
auth/network/SDK or other unexpected errors so the overwrite: false preflight
used by the write/copy/move call sites remains reliable.
In `@workspaces/mesa/src/provider.ts`:
- Around line 15-21: The Mesa provider schema currently allows an empty repos
array even though MesaFilesystem.init() rejects it at runtime; update the schema
in provider.ts so the repos property enforces at least one entry. Use the
existing repos property definition in the schema (and the MesaFilesystem.init()
contract) to locate the change, and add the appropriate array constraint so
invalid empty configs fail validation instead of initialization.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 78b53b0b-7996-42ea-8184-06ce7f691721
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (20)
.changeset/few-planets-invite.mdMESA_INTEGRATION_PLAN.mddocs/src/content/en/docs/workspace/filesystem.mdxdocs/src/content/en/reference/workspace/mesa-filesystem.mdxpnpm-workspace.yamlworkspaces/mesa/CHANGELOG.mdworkspaces/mesa/README.mdworkspaces/mesa/eslint.config.jsworkspaces/mesa/lint-staged.config.jsworkspaces/mesa/package.jsonworkspaces/mesa/src/filesystem/index.integration.test.tsworkspaces/mesa/src/filesystem/index.test.tsworkspaces/mesa/src/filesystem/index.tsworkspaces/mesa/src/index.tsworkspaces/mesa/src/provider.test.tsworkspaces/mesa/src/provider.tsworkspaces/mesa/tsconfig.build.jsonworkspaces/mesa/tsconfig.jsonworkspaces/mesa/tsup.config.tsworkspaces/mesa/vitest.config.ts
Comment on lines
+23
to
+25
| if (!process.env.MESA_API_KEY) { | ||
| throw new Error('MesaFilesystem integration tests require MESA_API_KEY.'); | ||
| } |
Contributor
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
Skip these integration tests when MESA_API_KEY is missing.
Throwing at module load makes the entire Vitest run fail on machines or CI where the secret is intentionally absent. The PR summary describes these as environment-gated tests, so this should register skipped tests instead of aborting collection.
Suggested fix
-import { afterAll, describe, expect, it } from 'vitest';
+import { afterAll, describe, expect, it } from 'vitest';
...
-if (!process.env.MESA_API_KEY) {
- throw new Error('MesaFilesystem integration tests require MESA_API_KEY.');
-}
+const hasMesaApiKey = Boolean(process.env.MESA_API_KEY);
+const describeMesa = hasMesaApiKey ? describe : describe.skip;
...
-describe('MesaFilesystem integration', () => {
+describeMesa('MesaFilesystem integration', () => {
...
});
-createFilesystemTestSuite({
- suiteName: 'MesaFilesystem Conformance',
- createFilesystem: async () => {
- const testRoot = await mesaRepoPath(`conformance-${Date.now()}-${Math.random().toString(36).slice(2, 8)}`);
- return new RootedMesaFilesystem(await createMesaFilesystem(), testRoot);
- },
- cleanupFilesystem: async fs => {
- await fs.rmdir('/', { recursive: true, force: true }).catch(() => {});
- },
- capabilities: {
- supportsAppend: true,
- supportsBinaryFiles: true,
- supportsMounting: false,
- supportsForceDelete: true,
- supportsOverwrite: true,
- supportsConcurrency: true,
- supportsEmptyDirectories: true,
- deleteThrowsOnMissing: true,
- },
- testTimeout: 30000,
-});
+if (hasMesaApiKey) {
+ createFilesystemTestSuite({
+ suiteName: 'MesaFilesystem Conformance',
+ createFilesystem: async () => {
+ const testRoot = await mesaRepoPath(`conformance-${Date.now()}-${Math.random().toString(36).slice(2, 8)}`);
+ return new RootedMesaFilesystem(await createMesaFilesystem(), testRoot);
+ },
+ cleanupFilesystem: async fs => {
+ await fs.rmdir('/', { recursive: true, force: true }).catch(() => {});
+ },
+ capabilities: {
+ supportsAppend: true,
+ supportsBinaryFiles: true,
+ supportsMounting: false,
+ supportsForceDelete: true,
+ supportsOverwrite: true,
+ supportsConcurrency: true,
+ supportsEmptyDirectories: true,
+ deleteThrowsOnMissing: true,
+ },
+ testTimeout: 30000,
+ });
+}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| if (!process.env.MESA_API_KEY) { | |
| throw new Error('MesaFilesystem integration tests require MESA_API_KEY.'); | |
| } | |
| const hasMesaApiKey = Boolean(process.env.MESA_API_KEY); | |
| const describeMesa = hasMesaApiKey ? describe : describe.skip; |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@workspaces/mesa/src/filesystem/index.integration.test.ts` around lines 23 -
25, The module-level MESA_API_KEY guard in the integration test file is aborting
Vitest collection instead of skipping these tests. Move the check out of
top-level execution and gate the suite or individual tests in the existing
MesaFilesystem integration test setup so they register as skipped when
MESA_API_KEY is missing, using the test suite entrypoints in
index.integration.test.ts rather than throwing during import.
abhiaiyer91
approved these changes
Jun 29, 2026
warrenbhw
force-pushed
the
warrenbhw/mesa-filesystem-integration
branch
from
b25f445 to
35dd62f
Compare
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (2)
workspaces/mesa/src/filesystem/index.integration.test.ts (2)
212-215: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick winReject rooted paths that escape the test sandbox.
path.join(this.root, normalized)is still not containment-safe here: inputs like../siblingresolve outsidethis.root, so the adapter can read/write/delete sibling repo paths and break test isolation.Suggested fix
private toMesaPath(inputPath: string): string { const normalized = path.normalize(inputPath || '/'); if (normalized === '/') return this.root; - return path.join(this.root, normalized); + + const candidate = path.resolve(this.root, normalized.replace(/^\/+/, '')); + if (candidate !== this.root && !candidate.startsWith(`${this.root}/`)) { + throw new Error(`Path escapes rooted Mesa filesystem: ${inputPath}`); + } + + return candidate; }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@workspaces/mesa/src/filesystem/index.integration.test.ts` around lines 212 - 215, The toMesaPath helper in the Mesa filesystem test adapter is not containment-safe because path.join(this.root, normalized) can still escape the sandbox for rooted or relative traversal inputs like ../sibling. Update toMesaPath to canonicalize the candidate path and verify it stays within this.root before returning it, rejecting any path that resolves outside the test root. Use the existing toMesaPath method in index.integration.test.ts as the place to enforce this boundary check.
36-41: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick winSkip the integration suite when Mesa credentials are absent.
These tests are still environment-gated in intent, but
beforeAllcurrently throws and fails the run instead of marking the suite as skipped whenMESA_API_KEYis missing. Gate the suite/conformance registration behind a boolean and usedescribe.skipwhen credentials are unavailable.Suggested fix
import { afterAll, beforeAll, describe, expect, it } from 'vitest'; @@ -let mesaTestEnv: MesaTestEnv | undefined; +let mesaTestEnv: MesaTestEnv | undefined; +const hasMesaApiKey = Boolean(process.env.MESA_API_KEY); @@ beforeAll(async () => { const apiKey = process.env.MESA_API_KEY; if (!apiKey) { - throw new Error('MesaFilesystem integration tests require MESA_API_KEY.'); + return; } @@ -describe('MesaFilesystem integration', () => { +(hasMesaApiKey ? describe : describe.skip)('MesaFilesystem integration', () => { @@ -createFilesystemTestSuite({ - suiteName: 'MesaFilesystem Conformance', - createFilesystem: async () => { - const testRoot = mesaRepoPath(`conformance-${Date.now()}-${Math.random().toString(36).slice(2, 8)}`); - return new RootedMesaFilesystem(createMesaFilesystem(), testRoot); - }, - cleanupFilesystem: async fs => { - await fs.rmdir('/', { recursive: true, force: true }).catch(() => {}); - }, - capabilities: { - supportsAppend: true, - supportsBinaryFiles: true, - supportsMounting: false, - supportsForceDelete: true, - supportsOverwrite: true, - supportsConcurrency: true, - supportsEmptyDirectories: true, - deleteThrowsOnMissing: true, - }, - testTimeout: 30000, -}); +if (hasMesaApiKey) { + createFilesystemTestSuite({ + suiteName: 'MesaFilesystem Conformance', + createFilesystem: async () => { + const testRoot = mesaRepoPath(`conformance-${Date.now()}-${Math.random().toString(36).slice(2, 8)}`); + return new RootedMesaFilesystem(createMesaFilesystem(), testRoot); + }, + cleanupFilesystem: async fs => { + await fs.rmdir('/', { recursive: true, force: true }).catch(() => {}); + }, + capabilities: { + supportsAppend: true, + supportsBinaryFiles: true, + supportsMounting: false, + supportsForceDelete: true, + supportsOverwrite: true, + supportsConcurrency: true, + supportsEmptyDirectories: true, + deleteThrowsOnMissing: true, + }, + testTimeout: 30000, + }); +}Also applies to: 256-276
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@workspaces/mesa/src/filesystem/index.integration.test.ts` around lines 36 - 41, The MesaFilesystem integration suite currently throws in beforeAll when MESA_API_KEY is missing, which fails the run instead of skipping it. Update the registration in index.integration.test.ts to compute a credentials-available boolean first, then choose between describe and describe.skip for the suite/conformance block. Keep the existing MesaFilesystem test setup inside the gated describe so the integration tests are skipped cleanly when credentials are absent.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@workspaces/mesa/src/filesystem/index.integration.test.ts`:
- Around line 212-215: The toMesaPath helper in the Mesa filesystem test adapter
is not containment-safe because path.join(this.root, normalized) can still
escape the sandbox for rooted or relative traversal inputs like ../sibling.
Update toMesaPath to canonicalize the candidate path and verify it stays within
this.root before returning it, rejecting any path that resolves outside the test
root. Use the existing toMesaPath method in index.integration.test.ts as the
place to enforce this boundary check.
- Around line 36-41: The MesaFilesystem integration suite currently throws in
beforeAll when MESA_API_KEY is missing, which fails the run instead of skipping
it. Update the registration in index.integration.test.ts to compute a
credentials-available boolean first, then choose between describe and
describe.skip for the suite/conformance block. Keep the existing MesaFilesystem
test setup inside the gated describe so the integration tests are skipped
cleanly when credentials are absent.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 3a3efc3d-b6db-423c-8909-0eed466b10af
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (20)
.changeset/few-planets-invite.mdMESA_INTEGRATION_PLAN.mddocs/src/content/en/docs/workspace/filesystem.mdxdocs/src/content/en/reference/workspace/mesa-filesystem.mdxpnpm-workspace.yamlworkspaces/mesa/CHANGELOG.mdworkspaces/mesa/README.mdworkspaces/mesa/eslint.config.jsworkspaces/mesa/lint-staged.config.jsworkspaces/mesa/package.jsonworkspaces/mesa/src/filesystem/index.integration.test.tsworkspaces/mesa/src/filesystem/index.test.tsworkspaces/mesa/src/filesystem/index.tsworkspaces/mesa/src/index.tsworkspaces/mesa/src/provider.test.tsworkspaces/mesa/src/provider.tsworkspaces/mesa/tsconfig.build.jsonworkspaces/mesa/tsconfig.jsonworkspaces/mesa/tsup.config.tsworkspaces/mesa/vitest.config.ts
✅ Files skipped from review due to trivial changes (7)
- workspaces/mesa/tsconfig.build.json
- workspaces/mesa/CHANGELOG.md
- workspaces/mesa/src/index.ts
- workspaces/mesa/README.md
- .changeset/few-planets-invite.md
- docs/src/content/en/reference/workspace/mesa-filesystem.mdx
- workspaces/mesa/lint-staged.config.js
🚧 Files skipped from review as they are similar to previous changes (10)
- workspaces/mesa/vitest.config.ts
- workspaces/mesa/eslint.config.js
- workspaces/mesa/tsconfig.json
- workspaces/mesa/src/provider.test.ts
- workspaces/mesa/src/provider.ts
- workspaces/mesa/tsup.config.ts
- workspaces/mesa/package.json
- pnpm-workspace.yaml
- workspaces/mesa/src/filesystem/index.test.ts
- workspaces/mesa/src/filesystem/index.ts
warrenbhw
force-pushed
the
warrenbhw/mesa-filesystem-integration
branch
from
35dd62f to
4641385
Compare
warrenbhw
force-pushed
the
warrenbhw/mesa-filesystem-integration
branch
from
4641385 to
c28f61e
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@MESA_INTEGRATION_PLAN.md`:
- Around line 118-121: The Agent example in MESA_INTEGRATION_PLAN.md still uses
the unexpanded __GATEWAY_ANTHROPIC_MODEL_OPUS__ placeholder, so make the snippet
copy-pasteable by replacing it with a real model string or clearly labeling it
as docs-only; update the Agent initialization example (the one setting name,
model, and workspace) to use an actual value consistent with this repo’s docs
conventions, since placeholder expansion only happens in docs/src MDX files and
changesets.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 49d4cc19-5a01-4a0b-9a62-28248bf254cc
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (20)
.changeset/few-planets-invite.mdMESA_INTEGRATION_PLAN.mddocs/src/content/en/docs/workspace/filesystem.mdxdocs/src/content/en/reference/workspace/mesa-filesystem.mdxpnpm-workspace.yamlworkspaces/mesa/CHANGELOG.mdworkspaces/mesa/README.mdworkspaces/mesa/eslint.config.jsworkspaces/mesa/lint-staged.config.jsworkspaces/mesa/package.jsonworkspaces/mesa/src/filesystem/index.integration.test.tsworkspaces/mesa/src/filesystem/index.test.tsworkspaces/mesa/src/filesystem/index.tsworkspaces/mesa/src/index.tsworkspaces/mesa/src/provider.test.tsworkspaces/mesa/src/provider.tsworkspaces/mesa/tsconfig.build.jsonworkspaces/mesa/tsconfig.jsonworkspaces/mesa/tsup.config.tsworkspaces/mesa/vitest.config.ts
✅ Files skipped from review due to trivial changes (9)
- workspaces/mesa/CHANGELOG.md
- workspaces/mesa/src/index.ts
- .changeset/few-planets-invite.md
- workspaces/mesa/tsup.config.ts
- workspaces/mesa/tsconfig.build.json
- workspaces/mesa/README.md
- docs/src/content/en/reference/workspace/mesa-filesystem.mdx
- workspaces/mesa/lint-staged.config.js
- pnpm-workspace.yaml
🚧 Files skipped from review as they are similar to previous changes (8)
- workspaces/mesa/src/provider.test.ts
- workspaces/mesa/tsconfig.json
- workspaces/mesa/eslint.config.js
- workspaces/mesa/src/provider.ts
- workspaces/mesa/vitest.config.ts
- workspaces/mesa/package.json
- workspaces/mesa/src/filesystem/index.test.ts
- workspaces/mesa/src/filesystem/index.ts
Add a new @mastra/mesa workspace filesystem package backed by Mesa repos. Document the provider, include focused unit and integration test coverage, and add the release changeset.
warrenbhw
force-pushed
the
warrenbhw/mesa-filesystem-integration
branch
from
c28f61e to
e6b154e
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@workspaces/mesa/src/filesystem/index.integration.test.ts`:
- Around line 65-68: The cleanup helpers, including deleteMesaTestRepo and the
other shared Mesa teardown paths in this test file, are swallowing all errors
with blanket catch blocks, which hides real mutation failures. Update the
cleanup logic to only ignore the expected “already gone/not found” case and
rethrow or fail on any other error, so repo/root deletion issues surface instead
of being silently skipped.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 1634d51d-fc0b-4e19-ac37-95ebc080c7ac
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (20)
.changeset/few-planets-invite.mdMESA_INTEGRATION_PLAN.mddocs/src/content/en/docs/workspace/filesystem.mdxdocs/src/content/en/reference/workspace/mesa-filesystem.mdxpnpm-workspace.yamlworkspaces/mesa/CHANGELOG.mdworkspaces/mesa/README.mdworkspaces/mesa/eslint.config.jsworkspaces/mesa/lint-staged.config.jsworkspaces/mesa/package.jsonworkspaces/mesa/src/filesystem/index.integration.test.tsworkspaces/mesa/src/filesystem/index.test.tsworkspaces/mesa/src/filesystem/index.tsworkspaces/mesa/src/index.tsworkspaces/mesa/src/provider.test.tsworkspaces/mesa/src/provider.tsworkspaces/mesa/tsconfig.build.jsonworkspaces/mesa/tsconfig.jsonworkspaces/mesa/tsup.config.tsworkspaces/mesa/vitest.config.ts
✅ Files skipped from review due to trivial changes (7)
- workspaces/mesa/vitest.config.ts
- workspaces/mesa/src/index.ts
- workspaces/mesa/tsconfig.json
- workspaces/mesa/README.md
- docs/src/content/en/reference/workspace/mesa-filesystem.mdx
- workspaces/mesa/tsconfig.build.json
- .changeset/few-planets-invite.md
🚧 Files skipped from review as they are similar to previous changes (10)
- workspaces/mesa/tsup.config.ts
- workspaces/mesa/src/provider.test.ts
- workspaces/mesa/CHANGELOG.md
- pnpm-workspace.yaml
- workspaces/mesa/package.json
- workspaces/mesa/src/provider.ts
- workspaces/mesa/lint-staged.config.js
- workspaces/mesa/eslint.config.js
- workspaces/mesa/src/filesystem/index.test.ts
- workspaces/mesa/src/filesystem/index.ts
Contributor
|
I've addressed all CodeRabbit and Superagent review comments in commit Changes made:
@warrenbhw you can cherry-pick this commit: |
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
2 participants
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.
Description
Adds a new
@mastra/mesaworkspace filesystem provider backed by Mesa repos. The provider mounts repos through the Mesa SDK, implements the Mastra workspace filesystem interface, and exposes Mesa-specific helpers likebash(),change,bookmark, and the mountedfilesystemfor advanced use.Also adds docs, README usage, focused unit/integration test coverage, a changeset, and the lockfile/package workspace updates needed for
@mesadev/sdk@0.38.0.TODO: need to work with Mastra core team to add Mesa credentials to secrets manager so integration tests will run in CI
Validated with:
corepack pnpm --filter ./workspaces/mesa test:unitcorepack pnpm --filter ./workspaces/mesa buildcorepack pnpm --filter ./workspaces/mesa lintcorepack pnpm --filter ./docs buildRelated issue(s)
#18629
Type of change
Checklist
ELI5
This adds a new way for Mastra workspaces to use Mesa as their file storage. In simple terms, it lets Mastra read and manage files inside Mesa repositories, and it also adds docs, tests, and package setup so people can use it safely.
What changed
@mastra/mesaworkspace package with a Mesa-backedMesaFilesystemprovider.bash(),change,bookmark, and the mountedfilesystem.@mesadev/sdk@0.38.0.Notable refinements
existschecks instead of treating them as missing files.