The production bot tracks a SEPARATE image, conjurer-bot-deploy, promoted
only when a commit message contains [deploy]. On such a 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 it. The
test bot + librarian keep updating on every build.
Merging THIS commit is deliberately the FIRST [deploy]: it lands the
promotion step AND carries the trigger, so it bootstraps conjurer-bot-deploy
to this build - a clean baseline with every image at the same, current version.
[deploy]
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
gitea