Commit Graph

4 Commits

Author SHA1 Message Date
gitea 41050fa879 ci: promote bot to a 'deploy' image channel only on [deploy] trigger
CI / compile (pull_request) Successful in 8s
CI / unit (pull_request) Successful in 26s
CI / integration (pull_request) Successful in 28s
The production bot tracks a separate image, conjurer-bot-deploy, so it
updates only when a commit message contains [deploy] - the test bot and
librarian keep updating on every build. On a [deploy] commit the already-
built conjurer-bot:<sha> is re-tagged (same bytes, no rebuild) and pushed
as conjurer-bot-deploy:<sha>; the deploy repo's image-updater tracks that.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-08-03 20:10:21 +02:00
gitea c8aae10671 build-radio change
build / build (push) Successful in 43m17s
CI / compile (push) Successful in 1m24s
CI / unit (push) Successful in 47s
CI / integration (push) Failing after 1m38s
2026-07-28 12:56:14 +02:00
gitea c95ce7d66c Build action
CI / compile (push) Successful in 51s
CI / unit (push) Successful in 49s
CI / integration (push) Failing after 49s
build / build (push) Failing after 14m50s
2026-07-26 15:36:22 +02:00
gitea 7b0029eecc Fix workflow 2026-07-21 22:50:57 +02:00