feat(storage): object migration methods#82
Conversation
Greptile SummaryThis PR adds
Confidence Score: 4/5Safe to merge after confirming the One P1 logic concern in the new packages/storage/src/lib/object/migrate.ts — specifically the Important Files Changed
Reviews (1): Last reviewed commit: "feat(storage): object migration methods" | Re-trigger Greptile |
There was a problem hiding this comment.
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 29161e2. Configure here.
29161e2 to
9010792
Compare
|
🎉 This PR is included in version 3.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |

Note
Medium Risk
Adds new storage API methods that trigger and detect object migration via custom headers, which could change runtime behavior when used. Also centralizes error handling across object ops and tweaks build/dev scripts, so regressions would mostly be in SDK responses and build pipelines.
Overview
Adds object migration support to the storage SDK via new
migrate()andisMigrated()helpers that issueHeadObjectrequests with/inspect newX-Tigris-*headers, and exports these methods fromserver.ts.Extends object listing to optionally request results from a specified source (
tigrisvsshadow) and now returnscommonPrefixesalongside items.Unifies error handling by removing per-function
handleErrorimplementations in storage object ops and using the sharedhandleError, updates config typing to allow partial env maps, and changes workspacebuild/devscripts to runtsc --noEmitbeforetsup(and makes rootdevignore missing scripts).Reviewed by Cursor Bugbot for commit 9010792. Bugbot is set up for automated code reviews on this repo. Configure here.