4 Commits

Include renames

Author	SHA1	Message	Date
magnusandClaude Opus 5	7ea25ee4fd	Retry the Harbor manifest copy instead of a probe for it ... The companion SHA tag step failed on the last build even though the image had already been pushed and deployed. Harbor's vulnerability policy blocks manifest reads while Trivy's scan is Running, and `imagetools create` copies the manifest, so Harbor answered 412 Precondition Failed. Two faults compounded. The loop gated on `imagetools inspect`, but a probe passing is no guarantee the copy will be allowed. And `create` sat outside the condition, so under the default `bash -e` its first failure aborted the step before `exit 0` or any further attempt: the log shows one waiting line, then the error, with 58 of 60 retries unused. Retry the real operation instead, inside the condition so a blocked copy is a reason to wait rather than fatal. The trade-off is that a permanently failing copy now takes the full ten minutes to report instead of failing fast; the previous behaviour failed fast but wrongly, on a transient block. Also records that only the primary tag matters for rollout, since the Flux image policy matches the timestamp tag, so a failure in this step costs the audit tag rather than the deployment. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-11 09:56:26 +02:00
magnus	b30637ee4e	Add pull request deployment workflow	2026-09-17 14:00:26 +02:00
magnus	9b42497e58	Avoid unavailable act runner cache service	2026-09-15 17:50:19 +02:00
magnus	0470862cb4	Build and publish btcprice images in Gitea Actions	2026-09-15 17:16:35 +02:00