8 Commits

Include renames

Author	SHA1	Message	Date
openhands	fabd160250	fix(ci): bound Docker build cache with BuildKit cache mounts ... - Move the pnpm store, apk and .next caches into --mount=type=cache so dependencies are shared across builds instead of duplicated in fresh image layers (was the source of unbounded disk growth). - Replace the deprecated --keep-storage prune flag in ci-deploy.sh with the working --max-used-space=4g (buildx v0.37 renamed the flag). The deprecated flag silently did nothing, so the BuildKit cache kept growing unbounded (was 15.86GB); it is now capped at 4GB after every deploy.	2026-09-08 15:39:13 +02:00
Simo	fe1ee8a6fe	fix(deploy): replace both legacy and CI containers during cutover	2026-09-07 21:40:26 +02:00
Simo	6cbcb50191	chore(deploy): identify the existing CMS listener before cutover	2026-09-07 21:35:17 +02:00
Simo	c35fc764bc	fix(deploy): wait for the expected HTTP release and report failed probes	2026-09-07 21:28:18 +02:00
Simo	cbaa115d56	fix(deploy): verify Docker clone updates against the served release	2026-09-07 21:17:34 +02:00
openhands	a640e40a5d	fix(docker): clear build cache on every build to stop unbounded disk growth	2026-09-07 16:18:04 +02:00
openhands	1a9b361420	fix(docker): inject real commit id into build via NEXT_DEPLOYMENT_ID ... next.config.ts falls back to `git rev-parse HEAD`, but the build context has no .git (excluded by .dockerignore), so every CI build printed fatal git errors and stamped the release as "unknown". Pass the deploy commit sha as a NEXT_DEPLOYMENT_ID build-arg so git is never invoked and the actual commit reaches NEXT_PUBLIC_CMS_RELEASE and deploymentId.	2026-09-07 11:39:29 +02:00
Simo	7c1f109a9d	ci: serialize deployments and restore previous release on smoke failure	2026-09-06 11:48:20 +02:00