Preserve Docker toolchain layers across release SHAs #32

Open AtlantisPleb opened this 6h ago

The production image build invalidates expensive operating-system, Node.js, Codex, and OpenCode layers for every source SHA because OPENAGENTS_BUILD_REVISION becomes an ENV value before those installation steps. Move revision-dependent instructions below stable toolchain installation, or split the stable toolchain into a pinned base image. Keep the embedded revision label and OpenAgents.BuildInfo exact-SHA checks unchanged. Acceptance: two adjacent source revisions reuse all dependency-independent toolchain layers, the image still embeds the exact candidate SHA, and the release gate verifies both properties.

  1. AtlantisPleb opened this issue 6h ago
Sign in with GitHub to comment on this issue.