82212165f9
fix(ci): trigger image builds on every path the Dockerfile copies
...
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 25s
The build filtered on api/** while the Dockerfile COPYs nine more paths, so
changes to mcp_server/, flows/, policies/, prompts/, scripts/,
task_flow_engine/, templates/, alembic.ini and — most seriously —
migrations/ merged to main without ever producing a new image.
A schema migration would not have shipped.
Refs CUST-WP-0067-T08
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-24 23:00:57 +02:00
1cf949bda4
feat(edge): add offline read cache for allowlisted State Hub GET routes
...
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 51s
The edge relay now persists successful GET responses and serves them with
stale markers when upstream is unreachable. Extend Forgejo image workflow
path filters so api changes trigger registry publishes.
2026-07-09 01:04:15 +02:00
0ca9c27035
ci: bump DEPS_LOCK_ID to 10 for working-memory sweep image rebuild
...
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 48s
Triggers Forgejo image workflow to publish main-<sha> with
consistency_check working-memory commit support (5289ba0
2026-07-07 01:09:11 +02:00
375961c69b
ci: bump DEPS_LOCK_ID to 9 for phase4 sweep image rebuild
...
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 32s
Triggers Forgejo image workflow to publish main-<sha> replacing the
hand-imported main-phase4-sweep tag on railiance01.
2026-07-06 20:14:11 +02:00
d1a4fcffa9
fix(ci): single RUN for deps + uv install on legacy DinD
...
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 14s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 1m2s
Legacy docker cannot chain shell after heredoc and does not persist
/tmp between RUN steps. Use python -c and one RUN for requirements
generation and venv install.
2026-07-06 18:44:21 +02:00
3a7fe235b1
fix(ci): store requirements.txt under /app not /tmp
...
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Build and Publish Multi-Context Image / build-and-push (push) Failing after 12s
DinD legacy builder does not persist /tmp across RUN steps, so uv pip
install could not find requirements.txt on the next layer.
2026-07-06 18:42:32 +02:00
1ac39da511
fix(ci): write requirements.txt in Python; bust DinD COPY cache
...
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Multi-Context Image / build-and-push (push) Failing after 19s
DinD legacy builder left requirements.txt empty when using shell redirect
on a cached COPY pyproject.toml layer. Write deps from Python directly,
add .ci-build-id COPY in CI, and preflight grep asyncpg in buildctx.
2026-07-06 18:40:55 +02:00
96b730653f
fix(ci): reference DEPS_LOCK_ID in RUN to invalidate DinD cache
...
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Build and Publish Multi-Context Image / build-and-push (push) Failing after 10s
ARG-only bumps did not invalidate cached empty requirements layers on
legacy docker. Echo the lock id in the deps RUN step.
2026-07-06 18:36:09 +02:00
dffa704cd5
fix(ci): bust DinD deps cache without full --no-cache rebuild
...
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 21s
Build and Publish Multi-Context Image / build-and-push (push) Failing after 33s
Full --no-cache exceeded runner time budget. Use DEPS_LOCK_ID build-arg
and fail-fast checks on requirements.txt instead.
2026-07-06 18:32:02 +02:00
8ee95dabb9
fix(ci): gate image build on asyncpg and disable DinD layer cache
...
CI Smoke / host-smoke (push) Successful in 2s
CI Smoke / container-smoke (push) Successful in 16s
Build and Publish Multi-Context Image / build-and-push (push) Failing after 1m57s
The main-f9f0091 Forgejo image shipped with an empty venv (0-byte
requirements.txt). Add Dockerfile RUN verification, --no-cache on CI
build, and a post-build import smoke test before push.
2026-07-06 18:28:11 +02:00
f9f0091cfe
Fix image workflow: vendor hub-core for legacy DinD docker (no buildx)
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 2m2s
2026-07-06 12:53:33 +02:00
ba58365ab7
Fix image workflow: use short SHA for Forgejo archive checkout
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 5s
Build and Publish Multi-Context Image / build-and-push (push) Failing after 16s
2026-07-06 12:49:46 +02:00
d8246577db
Fix image workflow: fetch extra repos from main, not primary SHA
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Multi-Context Image / build-and-push (push) Failing after 10s
2026-07-06 12:48:11 +02:00
817bdde604
Add Forgejo CI smoke and multi-repo image workflow (tier 3 T04)
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Multi-Context Image / build-and-push (push) Has been cancelled
2026-07-06 12:33:10 +02:00
