fix(deploy): the image manifest stages know the new workspace members
The images resolve the whole workspace graph before cargo fetch, so every member manifest has to be in the build context by then, and the copied list had fallen six crates behind the workspace: the backend split added sandbox-local, sandbox-lxd, and sandbox-server, and the cloud frontends added cloud-agent, cloudflare-code, and vercel-agent. rhema-code path-depends on the sandbox backends, so the claw image was the first to break — the fetch died reading the lxd manifest.
This commit is contained in:
1 parent
e92739aa1b
commit
06c03724c8
2 files changed
+7
No files matched your search
@@ -36,6 +36,7 @@ COPY crates/rhema-sandbox/Cargo.toml crates/rhema-sandbox/Cargo.toml
|
||||
COPY crates/rhema-sandbox-docker/Cargo.toml crates/rhema-sandbox-docker/Cargo.toml
|
||||
COPY crates/rhema-sandbox-http/Cargo.toml crates/rhema-sandbox-http/Cargo.toml
|
||||
COPY crates/rhema-sandbox-local/Cargo.toml crates/rhema-sandbox-local/Cargo.toml
|
||||
COPY crates/rhema-sandbox-lxd/Cargo.toml crates/rhema-sandbox-lxd/Cargo.toml
|
||||
COPY crates/rhema-sandbox-server/Cargo.toml crates/rhema-sandbox-server/Cargo.toml
|
||||
COPY crates/rhema-sandbox-ssh/Cargo.toml crates/rhema-sandbox-ssh/Cargo.toml
|
||||
COPY crates/rhema-subagents/Cargo.toml crates/rhema-subagents/Cargo.toml
|
||||
|
||||
Reference in new issue
Block a user