v0.6.65: memory fix, image uploads in files

[waleedlatif1]

• fix(memory): return 200 with null data when memory key not found on GET (fix(memory): return 200 with null data when memory key not found on GET #4421)
• feat(files): allow image uploads in workspace files (feat(files): allow image uploads in workspace files #4419)
• fix(files): align upload route image extensions with picker (fix(files): align upload route image extensions with picker #4423)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 3, 2026 10:32am

[cursor]

PR Summary

Medium Risk
Changes the GET /api/memory/:id contract to return 200 with data: null instead of 404, which can affect client logic expecting errors. File upload/validation changes expand allowed types (images) and could expose edge cases in MIME/extension handling.

Overview
Updates GET /api/memory/[id] so a missing memory key returns 200 with { success: true, data: null } rather than a 404 error, and adds a matching test to ensure tool response parsing yields an empty memories array.

Extends workspace Files to support image uploads by adding SUPPORTED_IMAGE_EXTENSIONS (and additional image MIME types), including images in the file input accept list, and adding Images to file type labeling and filtering UI.

^{Reviewed by Cursor Bugbot for commit 14c93f6. Configure here.}

[greptile-apps]

Greptile Summary

This PR bundles two small improvements: the memory GET route now returns 200 with { success: true, data: null } instead of 404 when a key is not found, aligning the API contract with what transformResponse already expected; and workspace file uploads now support image formats by exporting SUPPORTED_IMAGE_EXTENSIONS from the validation module and wiring it through the files UI. Both changes are straightforward, well-tested, and low-risk.

Confidence Score: 4/5

Safe to merge — both changes are targeted fixes with no breaking behavior.

Only P2 findings: a missing image branch in getSupportedMimeTypes (exported but unused for images) and an inline MIME check inconsistent with the audio/video pattern. No correctness or security regressions introduced.

apps/sim/lib/uploads/utils/validation.ts — getSupportedMimeTypes does not handle the newly exported image extensions.

Important Files Changed

Filename	Overview
apps/sim/app/api/memory/[id]/route.ts	Changed GET to return 200 with null data instead of 404 when memory key not found, aligning with the tool's transformResponse behavior.
apps/sim/tools/memory/get.test.ts	Adds test coverage for the null-data 200 response, verifying that transformResponse returns empty memories array correctly.
apps/sim/lib/uploads/utils/validation.ts	Exports SUPPORTED_IMAGE_EXTENSIONS constant and expands image MIME types; replaces the old private dot-prefixed array with a shared typed constant. getSupportedMimeTypes does not handle image extensions but is not currently called with them.
apps/sim/app/workspace/[workspaceId]/files/files.tsx	Adds image upload support to workspace files: imports SUPPORTED_IMAGE_EXTENSIONS, adds image to type filter, and updates display labels. Image filtering uses inline startsWith check rather than a dedicated helper.

Comments Outside Diff (1)

1. apps/sim/lib/uploads/utils/validation.ts, line 275-279 (link)

   The getSupportedMimeTypes utility now implicitly covers image extensions (via SupportedMediaExtension) but returns an empty array for any image extension, silently failing. Adding an image branch keeps the function consistent and prevents future callers from getting unexpected empty results.

_{Reviews (1): Last reviewed commit: "feat(files): allow image uploads in work..." | Re-trigger Greptile}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 14c93f6. Configure here.}