1.11.2 — Fleet deploys require node and fleet proof

2026-08-10

Django-MOJO 1.11.2 automatically derives stable node identity from the host and prevents canary-only or failed proof from being reported as a healthy fleet deployment.

Changed

• Ordinary nodes now use the normalized system hostname for deployment proof. EDGE_NODE_ID remains an optional override for containers or platforms with ephemeral or duplicate hostnames.
• A released fleet remains pending until the reconciler collects UUID- and commit-bound proof from its frozen runner roster, then closes as converged, partial, or unknown.

Fixed

• Canary success is no longer exposed to the orchestrator before local proof is persisted, preventing a proof failure from releasing the fleet and then rolling the canary back.
• Canary-only success is no longer recorded as a healthy terminal fleet deployment.
• Edge integration tests now isolate process-wide deployment settings and incident hooks from parallel test modules.