Repository navigation
Move Sandbox to destination account with SDK 1.0.3 native scheduling - #2
Merged
Merged
Conversation
TimoWilhelm
changed the title
TimoWilhelm
marked this pull request as ready for review
October 27, 2026 22:09
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
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.
Moves production deployments to Cloudflare account
415516b7403708741d606f6930e89e3fand ports the demo from Sandbox SDK 0.10.3 to 1.0.3 with native Durable Object container scheduling, required by the destination account. Commands, files, persistent interpreters, terminals, previews, tunnels, file events, outbound auth, OpenCode and R2 mounts retain their existing user interfaces.GitHub Actions builds and deploys the exact main commit that passed CI with destination credentials. Runtime S3 credentials are bucket scoped; CI and S3 credentials expire January 25, 2027. Deployment details and the native scheduler’s account-level container limits are documented in DEPLOYMENT.md.
Validation: formatting, typecheck, Knip, production builds and branch CI passed. Destination deployment succeeded. Live checks passed for execution, files, Python/JavaScript persistence and isolation, R2 remount persistence, Workers AI, outbound auth, wildcard previews, watch SSE, terminal I/O/reconnect and OpenCode. Both domains use destination nameservers and active TLS. The approved Access zone exception keeps sandbox-sdk.site public; Devplat remains protected.