From 90e55e050213eec35282b2588dc6505933ddaa6d Mon Sep 17 00:00:00 2001 From: prez2307 Date: Mon, 20 Apr 2026 19:10:42 -0400 Subject: [PATCH] =?UTF-8?q?chore(infra):=20bump=20prod.tag=20to=202026.4.5?= =?UTF-8?q?-bf9f699=20=E2=80=94=20flips=20prod=20to=20extended=20image?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Prod was stuck on the "bootstrap" placeholder, so container-stack.ts fell through to the legacy upstream alpine/openclaw:2026.4.5 — which does not have clawhub (or gh, uv, etc.) baked in, and agents on prod hit "clawhub: not in PATH" when installing skills. Flipping to the same tag dev has been running (2026.4.5-bf9f699) so the multi-stage extended image rolls out to prod. After deploy, existing per-user services still launch from the task def revision registered at provision time — they'll need a re-register (resize or delete+recreate) to pick up the new base image. Co-Authored-By: Claude Opus 4.7 (1M context) --- openclaw-version.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openclaw-version.json b/openclaw-version.json index 5deb49964..b7cfd9713 100644 --- a/openclaw-version.json +++ b/openclaw-version.json @@ -6,6 +6,6 @@ "full": "alpine/openclaw:2026.4.5", "extendedImage": "877352799272.dkr.ecr.us-east-1.amazonaws.com/isol8/openclaw-extended", "dev": { "tag": "2026.4.5-bf9f699" }, - "prod": { "tag": "bootstrap" }, + "prod": { "tag": "2026.4.5-bf9f699" }, "notes": "Two image references coexist during the migration to the extended image. The legacy `image`/`tag`/`full` fields point at the upstream alpine/openclaw image used by current container-stack.ts (Task 1-8 of the plan). The new `extendedImage` + per-env `dev.tag`/`prod.tag` fields point at our custom ECR image used after Task 9 lands. The 'bootstrap' tag is a placeholder until the first CI build completes — it intentionally won't resolve, so any deploy referencing it before the first build will fail loudly." }