Repository navigation
Release creative Runtime tools on the production beta baseline - #50
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8378afc1c1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| COPY services/core/deploy/creative /opt/oac-creative | ||
| RUN sh /opt/oac-creative/install.sh | ||
| ENV OAC_RUNTIME_TOOL_ENV_FILE=/opt/oac-creative/tool-env.json \ | ||
| PLAYWRIGHT_BROWSERS_PATH=/opt/oac-creative/browsers |
There was a problem hiding this comment.
PLAYWRIGHT_BROWSERS_PATH is also written to /opt/oac-creative/tool-env.json by configure.mjs, so direct image processes inherit one copy while prepared Sessions consume another. If either path changes independently, browser behavior diverges by launch path; remove the duplicate image-level value and let consumers read the Runtime-owned tool environment.
AGENTS.md reference: AGENTS.md:L53-L55
Useful? React with 👍 / 👎.
1 participant
Production currently runs beta, which contains Runtime and artifact fixes beyond main. Integrate the creative Runtime changes from #49 onto beta without replacing those fixes. The E2B release workflow now selects creative tools by default, supports an explicit base profile and records/verifies the final wrapped Runtime image.
The changes add the pinned browser, FFmpeg/ffprobe, CJK fonts and Python venv tools, preserve the existing explicit tool environment and restore E2B system dependencies after packaging. Existing beta initialization and lifecycle behavior stays in place.
Validation: focused E2B tests and CI/documentation/name checks run on this beta integration; Linux CI is required before merge. No merge, cloud template build, configuration generation update or production deployment has been performed. Activation remains blocked pending explicit human merge-and-release approval. Lab integration: https://github.com/sandbase-lab/lab/pull/376.