2026
- 2026-08-251.19.2 — Faster repeated secret decryption and non-pooled test projects
django-mojo 1.19.2 removes repeated PBKDF2 work from hot secret-decryption paths and aligns generated test projects with the default non-pooled PostgreSQL behavior.
- 2026-08-251.19.1 — Emergency rollback of automatic PostgreSQL pooling
django-mojo 1.19.1 stops automatically enabling psycopg connection pools in PostgreSQL deployments after the default caused process-local pool exhaustion in long-running ASGI, realtime, and job workers.
- 2026-08-241.19.0 — Bounded PostgreSQL pooling and complete transactional email templates
django-mojo 1.19.0 uses bounded, health-checked psycopg 3 pools for PostgreSQL under ASGI, completes the built-in transactional account email templates, and treats paid database/cache redundancy as an explicit availability choice.
- 2026-08-241.18.3 — Actionable deployment failures and fleet rollout guidance
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.
- 2026-08-241.18.2 — Live runner channels and bounded deployment diagnostics
django-mojo 1.18.2 lets enforced publishers address live explicit runner IDs without naming workarounds, makes the typed deployment timeout effective for one-shot units, and returns a small useful journal excerpt when a deployment fails.
- 2026-08-241.18.1 — Legacy deploy adoption and consumer test tiers
django-mojo now lets existing application-user updater shims enter the typed deployment transaction without project edits, while consumer projects gain configurable test presets, package scaffolding, optional isolation enforcement, and tier-aware GitHub Actions.
- 2026-08-231.18.0 — Typed KISS deployments and reliable delegated ACME
django-mojo replaces the policy-heavy deployment path with a small typed transaction that checks Django, nginx, and real service health, while preserving migrations, mixed node roles, and mechanical rollback. Delegated ACME issuance also stops deadlocking behind incompatible hub and client timeouts,…
- 2026-08-231.17.1 — Command-free MojoSec and faster test runs
MojoSec can start reliably on standard Amazon Linux 2023 hosts without Python RPM bindings or package-manager commands, while the test runner gains faster, safer tiered execution and several shutdown and test-path fixes.
- 2026-08-231.17.0 — Role-aware fleets, content-node monitoring, fleet-once cron
A fleet with more than one kind of node can now be deployed entirely through the framework: a project declares which nginx, cron and systemd files each node role owns, and every box converges exactly its own set. MojoSec gains a content-serving profile whose tenant directories are genuinely watched…
- 2026-08-221.16.2 — Exact brownfield ingress and role-aware nodes
django-mojo lets brownfield AWS fleets bind NLBs to an exact pre-existing security group, explicitly control target-group client-address preservation, and declare which nodes run framework ASGI. Provisioning proves the ingress boundary and non-request nodes revoke request service before they can be…
- 2026-08-221.16.1 — UTF-8-safe TLS lineage convergence
Repository vhosts with ordinary UTF-8 comments now deploy without losing an issued Certbot lineage, while malformed UTF-8 and Unicode-confusable server names remain fail-closed.
- 2026-08-221.16.0 — Parallel Admin v2 and safe certificate convergence
django-mojo adds a parallel Admin v2 workspace across operations, apps, infrastructure, domains, access, settings, and Assistant while keeping the existing Admin available. Node deployment also preserves only a validated matching Certbot lineage, so repository vhost updates no longer replace a trust…
- 2026-08-221.15.28 — Application-owned fleet health checks
Brownfield AWS fleets can now bind each load-balancer target group to the application’s real readiness endpoint while existing managed deployments keep the historical `/api/version` behavior.
- 2026-08-221.15.27 — Remote agents and guarded AWS migration
django-mojo now lets operators connect external AI clients through OAuth 2.1-secured MCP, optionally grant explicit full REST access, and manage or revoke those connections from Admin. It also adds exact-reference brownfield fleet provisioning and rehearsed, journaled preserved-EIP NLB handoff and r…
- 2026-08-221.15.26 — Fresh nodes converge from the pinned framework
Fresh managed nodes now materialize the pinned django-mojo deployment contract before project convergence, and their instance role can resolve the exact public AL2023 image parameter required by provisioning.
- 2026-08-221.15.25 — Capacity follows provider truth
Admin capacity now keeps owned EC2, RDS, and ElastiCache members visible through provider transitions, scopes them to the declared MojoLand environment, and disables unsafe replay or controls until fresh AWS state is settled.
- 2026-08-221.15.24 — System Setup describes release-bucket CORS accurately
System Setup now distinguishes an already-permissive wildcard CORS rule from the missing dedicated portal-origin rule, so its warning tells operators exactly what is absent without claiming uploads are blocked.
- 2026-08-221.15.23 — System Setup reports complete readiness
System Setup now keeps complete readiness totals inside its safety limits, clearly reports omitted detail, and never offers a repair for a passing check.
- 2026-08-221.15.22 — WebApp routes survive address restore
Taking a WebApp offline and restoring its address now keeps its custom API and path routes instead of silently rebuilding only the managed sign-in routes.
- 2026-08-221.15.21 — Restored WebApp addresses reapply the live release
Putting an existing WebApp back on an address now starts a fresh fleet convergence for its already-current release instead of leaving the address on the welcome page.