deploy: build one combined E2B Runtime template - #6
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
The fork can deploy Core/Web but has no independent workflow to build the Runtime template used by E2B. Add e2b-template-build: dispatch from main, choose a pinned main/beta source revision, build the maintained Codex/Claude SDK/MiniMax stages and combine them into one Linux amd64 Runtime image, then create one immutable E2B template with the selected source's builder.
Use a dedicated e2b-build environment for E2B_API_KEY and E2B_API_URL. Credentials are scoped to settings/template steps, read from a private temporary key file, excluded from images and reports, and removed on exit. Report source SHA, image ID, packaged checksum and templateID:build_UUID in the run summary and artifact. No template activation, Core/Web deployment, database writes or model calls are performed.
Validation: actionlint, shellcheck, SDK custom endpoint resolution, executed source/HTTPS/key gates, offline build-orchestration fixtures including digest checks and early failure, git diff --check and a fresh independent review. Live cloud building has not run because the account key is not yet configured; endpoint template create/upload/build support remains to be verified on the first requested build.