Repository navigation
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.
Same-team E2B configuration changes can apply while existing Sessions keep their sandboxes. New allocations use the new immutable generation; existing allocations and pending placements retain their original specification. Node-provider online preparation is handled by the dependent node-generation PR.
Core retains generations while current, pinned or referenced, and routes retained E2B generations through the committed credential. Credential replacement verifies owned template/build identity, fences in-flight helper work, and commits the generation and audit atomically. Public readability alone does not establish ownership; uncertain or rejected replacements leave the active credential unchanged. Authoritative rollout and allocation-generation fields are exposed through the shared client and generated Core contracts. The public Agent API and machine schemas remain unchanged. Migration 81 follows PR #176's migration 80.
Validation on 1bb10f0: complete local server make-check gate and both CI workflows passed, alongside 119 E2B helper tests, 669 client tests, actual PostgreSQL/race regressions and independent ownership/lifecycle review. The exact private offline build passed archive/member checks, all eight node payload checks and four Runtime smoke checks; its archive SHA256 is 7d3f289121c2b99e3bd63d1b5f93081c995a2df8b2e3700bf3ab2ba139fad374. Real E2B same-key replacement and an actual immutable template/build change with retained live Sessions remain required before this draft is ready. Controlled ownership tests do not claim real cross-team qualification.
Stacked on PR #176. Browser acceptance is separate under the approved server exclusion. No intermediate release or live-demo/rehearsal upgrade.