deda0002ab
All checks were successful
deploy / deploy (push) Successful in 30s
Proof: Push-driven repo workflow now renders and applies the built image across all repo-owned deployments instead of resetting services to placeholder images or relying on a manual rollout list. Assumptions: All repo-owned workloads that should roll on push carry app.kubernetes.io/part-of= in the manifests, and namespace bootstrap can happen before the image build without applying placeholder deployments. Still fake: This turn fixes the repo deployment path in code, but I have not yet exercised the new Forgejo workflow end-to-end from a fresh push on the cluster. |
||
|---|---|---|
| .. | ||
| alert-engine.test.mjs | ||
| alert-notifier.test.mjs | ||
| armed-state-store.test.mjs | ||
| executor-state-store.test.mjs | ||
| funding-observations.test.mjs | ||
| inventory-and-history.test.mjs | ||
| json-state-store.test.mjs | ||
| legacy-schema-compat.test.mjs | ||
| liquidity-state.test.mjs | ||
| liquidity-withdrawals.test.mjs | ||
| operator-dashboard.test.mjs | ||
| portfolio-metrics.test.mjs | ||
| render_release_manifest_test.py | ||
| signing.test.mjs | ||
| strategy.test.mjs | ||