1.16.0 — Parallel Admin v2 and safe certificate convergence

2026-08-22

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 trusted certificate with the first-boot placeholder.

Added

• A parallel Admin v2 workspace at /admin/v2/ packages Home, Apps, Infrastructure, Domains, Access, Activity, Settings, messaging, System Setup, and Assistant operations behind a new six-destination shell.
• Admin v2 includes application deployment and serving workflows, capacity and stable outbound-address controls, DNS and certificate operations, security posture, edge-runner visibility, and user, group, and API-key management.

Changed

• Legacy Admin hashes resolve to their corresponding Admin v2 destinations, while records open as pages and focused actions use modals.
• Admin v2 capacity views retain per-member provider lifecycle truth and expose transitioning state instead of presenting unsettled resources as healthy.

Fixed

• Assistant discovery results no longer render an empty null value.
• Repository vhost deployment keeps a matching issued Certbot certificate and private-key pair while continuing to replace every other directive from repository state.

Security

• TLS-lineage preservation fails closed for renamed or ambiguous TLS servers, mixed or noncanonical paths, unsafe ownership or permissions, readable private keys, destination symlinks, writable configuration directories, and files that change during inspection. Refusal output does not disclose certificate paths.
• Vhost replacement stages and validates the new configuration through a pinned directory descriptor before atomic installation.

Upgrade notes

• No database migration is required. The existing Admin remains available at /admin/; Admin v2 is the parallel surface at /admin/v2/.
• Projects may keep an absolute non-Certbot certificate pair as their first-boot placeholder. Once a matching Certbot lineage exists, ordinary deploys preserve it; ambiguous or unsafe installed TLS state now stops vhost convergence instead of silently falling back to the placeholder.