Skip to content

chore(deps): move to the renamed @daytona/sdk package - #6033

Merged
waleedlatif1 merged 1 commit into
stagingfrom
deps-daytona-sdk
Jul 29, 2026
Merged

chore(deps): move to the renamed @daytona/sdk package#6033
waleedlatif1 merged 1 commit into
stagingfrom
deps-daytona-sdk

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

Split out of #6013 and kept deliberately small, because this is the one change here that cannot be fully verified by CI.

@daytonaio/sdk was 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 matching serverExternalPackages entry — no logic changes.

Verification, and its limit

daytona.create({...} as any) means tsc alone would not catch a signature change, so I checked the API surface directly against the installed 0.200.0 type declarations. All 14 members daytona.ts depends 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 without as any typechecks 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

  • Maintenance

Testing

tsc clean; 31 remote-sandbox conformance tests pass. No live sandbox run — see above.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@daytonaio/sdk was renamed upstream to @daytona/sdk; the old name stops
receiving releases. Import-specifier change only, plus the matching
serverExternalPackages entry.
@waleedlatif1
waleedlatif1 requested a review from a team as a code owner July 29, 2026 00:05
@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 29, 2026 12:09am

Request Review

@cursor

cursor Bot commented Jul 29, 2026

Copy link
Copy Markdown

PR Summary

Medium Risk
Touches the remote sandbox execution path (Daytona provider and Pi snapshot build), but it’s a package rename with a minor version bump; CI mocks don’t prove a live sandbox still works.

Overview
Replaces the deprecated @daytonaio/sdk (0.197.0) with @daytona/sdk (0.200.0) across the Sim app. Upstream renamed the package; behavior in this repo is unchanged aside from import paths and dependency metadata.

package.json and bun.lock swap the dependency and align @daytona/* client packages to 0.200.0; the lockfile also bumps root tar (7.5.16 → 7.5.22). next.config.ts lists @daytona/sdk under serverExternalPackages.

Runtime and tooling imports now use @daytona/sdk in daytona.ts, build-pi-daytona-snapshot.ts, and the Daytona mock in conformance.test.ts. No sandbox provider logic was modified.

Reviewed by Cursor Bugbot for commit dcd7792. Configure here.

@greptile-apps

greptile-apps Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Renames the Daytona client package from @daytonaio/sdk to @daytona/sdk and bumps it from 0.197.0 to 0.200.0.

  • Updates the dynamic import in the Daytona sandbox provider, the snapshot build script import, the Vitest mock specifier, and the Next.js serverExternalPackages entry.
  • Refreshes apps/sim/package.json and bun.lock for the new package name, version, and transitive resolution (including a new socket.io-client dependency on the SDK).

Confidence Score: 5/5

Safe 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 @daytonaio/sdk were updated to @daytona/sdk, the lockfile matches package.json, and no application logic changed. Residual risk is limited to unexercised live Daytona sandbox behavior, which is outside what this diff can break in-repo.

Important Files Changed

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

@waleedlatif1
waleedlatif1 merged commit 69b8364 into staging Jul 29, 2026
15 checks passed
@waleedlatif1
waleedlatif1 deleted the deps-daytona-sdk branch July 29, 2026 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant