1.18.3 — Actionable deployment failures and fleet rollout guidance

2026-08-24

django-mojo 1.18.3 makes deployment failures identify the exact fixed phase and whether rollback or publication recovery completed, prevents jobs CLI status from misreporting deployed jobman workers, and documents the correct upgrade path for existing fleets.

Fixed

• Failed deployments now retain a bounded phase such as django_check and report whether rollback completed or failed.
• Post-activation publication recovery now reports its own completed or failed result instead of claiming that the previous release was restored.
• An empty jobs CLI status now says it checked daemon-mode processes only and points operators to jobman for deployed foreground workers.

Upgrade notes

• Fleets on django-mojo 1.18.1 or newer that use the packaged updater or locator shim can upgrade through the Admin Framework Update action without per-node SSH.
• Older fleets and projects with vendored deployment scripts need one controlled fleet remote-execution bootstrap before returning to normal framework updates.