chore(deps): move to the renamed @daytona/sdk package - #6033
Conversation
@daytonaio/sdk was renamed upstream to @daytona/sdk; the old name stops receiving releases. Import-specifier change only, plus the matching serverExternalPackages entry.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryMedium Risk Overview
Runtime and tooling imports now use Reviewed by Cursor Bugbot for commit dcd7792. Configure here. |
Greptile SummaryRenames the Daytona client package from
Confidence Score: 5/5Safe to merge from a code-review perspective: the rename is complete and consistent across imports, config, tests, and the lockfile. All in-repo references to
|
| Filename | Overview |
|---|---|
| apps/sim/lib/execution/remote-sandbox/daytona.ts | Only the dynamic import specifier changes to @daytona/sdk; sandbox create/run/cleanup logic is untouched. |
| apps/sim/package.json | Dependency renamed to @daytona/sdk@0.200.0 to match the upstream package rename. |
| apps/sim/next.config.ts | serverExternalPackages entry updated so Next continues to externalize the renamed SDK. |
| apps/sim/lib/execution/remote-sandbox/conformance.test.ts | Vitest mock path updated to the new package name so conformance tests still intercept Daytona. |
| apps/sim/scripts/build-pi-daytona-snapshot.ts | Static import of Daytona and Image updated to @daytona/sdk. |
| bun.lock | Lockfile resolves @daytona/sdk@0.200.0 and drops the old @daytonaio/sdk entry. |
Reviews (1): Last reviewed commit: "chore(deps): move to the renamed @dayton..." | Re-trigger Greptile
Summary
Split out of #6013 and kept deliberately small, because this is the one change here that cannot be fully verified by CI.
@daytonaio/sdkwas renamed upstream to@daytona/sdk(0.197.0 → 0.200.0); the old name stops receiving releases. The source change is an import-specifier rename in four places plus the matchingserverExternalPackagesentry — no logic changes.Verification, and its limit
daytona.create({...} as any)meanstscalone would not catch a signature change, so I checked the API surface directly against the installed 0.200.0 type declarations. All 14 membersdaytona.tsdepends on are present (codeInterpreter.runCode,process.codeRun/executeCommand/createSession/executeSessionCommand/getSessionCommand/deleteSession,fs.downloadFile/uploadFile,sandbox.delete,Image), and a compile-only probe exercising every call shape withoutas anytypechecks clean.Still unproven: an actual sandbox launch. Nothing in the test suite talks to a real Daytona instance. Worth one live run against a dev key before merging.
Type of Change
Testing
tscclean; 31 remote-sandbox conformance tests pass. No live sandbox run — see above.Checklist