1.11.7 — MojoSec sensors accept previous-generation configs — fleet deploys unblocked

2026-08-14

django-mojo 1.11.7 unblocks fleets that 1.11.6 left unable to deploy: the MojoSec sensor now starts against a configuration written by an earlier version instead of crashing mid-deploy, ACME DNS-01 issuance waits for Route53 to actually be authoritative before asking for validation, and Admin modals stack correctly over drawers.

Fixed

• The MojoSec sensor starts against an effective configuration written by a previous version: the journal-collector fields 1.11.6 introduced now backfill from defaults for one generation instead of crashing the sensor. This was failing entire fleet deploys — post_deploy restarts the sensor on the just-installed version while the on-disk configuration is still the old one, so the crash failed the canary gate and the rollback behind it.
• An effective configuration missing a required field now fails with a clear configuration error naming the field, never a bare crash.
• ACME DNS-01 issuance threads each challenge record's change id into the propagation wait, so the Route53 INSYNC gate actually runs. Previously the gate was silently skipped and issuance could ask for validation before the record was live everywhere, failing with NXDOMAIN at the validator's vantage.
• Admin portal modals stack above open drawers instead of behind them.

Changed

• A Route53 propagation wait that runs without a change id now logs a warning — before, the INSYNC gate being off was invisible and the wait looked stricter than it was.
• A record upsert that converged through inventory reconciliation no longer passes its sentinel into the propagation wait; there is no change batch behind it to poll, and polling it could fail an otherwise-successful recovery.

Upgrade notes

• Fleets stuck failing deploys at post_deploy under 1.11.6 need no node-side action: once a deploy resolves this version, the sensor accepts the existing configuration and the next convergence rewrites it with the new fields.