Repository navigation
Build the sandbox image and a Linux amd64 installer - #567
Merged
Merged
Conversation
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
1 participant
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.
Package one Sandbox I/O image and a Linux amd64 self-hosted installer containing only the launcher and Sandbox I/O binary. Native Harnesses stay on the agent host; remove guest Runtime images, Harness installation/aliases/probes, obsolete bootstrap artifacts and unsupported installation archives. Portable Core operator launchers can still manage a Linux amd64 Docker engine.
Preserve onboarding claims, installation locking, interrupted-operation recovery and immutable installed programs. Reject unsupported native platforms before claims, prepare the declared workspace, retain existing node artifact names, and align release catalogs, client/Web/example and bilingual documentation. Sandbox security settings are narrowed with live Docker evidence. Current-source MiniMax companion verification prevents stale same-version payloads from entering a release.
Validation: Go build/vet and focused/race tests; shared cross-builds; actual agent-host/sandbox images and Docker lifecycle/recovery/Serve-Attach/node tests; disposable native onboarding smoke including lost response/retry/no duplicate launcher; installer/distribution/publisher/E2B fixtures; client/Web/example tests and typechecks; generated contracts and hygiene. Independent review findings addressed, including focused rejection tests on macOS/Windows CI. Browser E2E could not launch locally due to missing browser/system libraries; remote hosted qualification and complete release archive build remain final-cutover checks.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.