Chart 1.4.115 was published from the merge commit which still had the
OLD application-controller image tag (a3ba200) in values.yaml — the
auto-bump commit landed seconds later but GitHub Actions does NOT
trigger workflows from bot pushes by default (anti-recursion safeguard),
so blueprint-release was never re-run and the published chart shipped
with the wrong image. Sovereigns installing chart 1.4.115 still ran
the buggy application-controller without the targetNamespace fix.
Fix:
- Bump bp-catalyst-platform 1.4.115 → 1.4.116 (this commit is human-
authored so blueprint-release fires via the path filter).
- Bump clusters/_template/bootstrap-kit/13-bp-catalyst-platform.yaml
pin to 1.4.116.
- Extend build-application-controller.yaml to dispatch
blueprint-release.yaml after the bot bumps values.yaml, so the same
race never blocks any future controller image roll-out.
Per docs/INVIOLABLE-PRINCIPLES.md #1 (target-state) — operator must
never have to manually re-trigger a chart publish after a controller
image rebuild.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
9780e8d72d