Tagged 'release'
- 2026-08-141.11.7 — MojoSec sensors accept previous-generation configs — fleet deploys unblocked
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…
- 2026-08-141.11.10 — Deploy failures report themselves, and a release can no longer move every fleet at once
django-mojo 1.11.10 closes the two halves of the 2026-08-14 deploy outage: an update script that cannot run now reports exactly why and releases the deploy plane instead of wedging it silently, and a new operator-controlled framework version hold means a PyPI release no longer changes what fleets in…
- 2026-08-131.11.6 — Privileged provenance and durable WebApp onboarding
django-mojo 1.11.6 makes MojoSec privileged activity attributable and fail-open, routing expected firewall automation through a verified broker while preserving rich operator evidence, and adds replay-safe Admin onboarding that can create a new WebApp organization in place.
- 2026-08-121.11.5 — MojoSec integrity monitor ignores incomplete fast scans for RPM verification
django-mojo 1.11.5 fixes a MojoSec host-sensor bug where an incomplete fast filesystem scan could raise false package-deletion alerts and corrupt the RPM verification baseline.
- 2026-08-111.11.4 — Quieter MojoSec signals and terminal delivery
django-mojo 1.11.4 reduces noisy MojoSec alerts, makes receiver failures terminal and recoverable, fixes AL2023 integrity baselining, hardens system-event trust and admin password recovery, and accepts valid Next.js release paths.
- 2026-08-111.11.3 — Actionable Admin setup and self-healing nginx runtime paths
django-mojo 1.11.3 adds a curated Admin Settings home, makes Setup and live QA feedback actionable, fixes evidence and datetime rendering, and automatically converges nginx runtime directories during deployment.
- 2026-08-101.11.2 — Fleet deploys require node and fleet proof
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.
- 2026-08-101.11.1 — Fleet deploys use complete, bounded runner rosters
Django-MOJO 1.11.1 fixes fleet deployment failures in large Redis keyspaces and applies the same fail-closed, complete-roster guarantee to platform and WebApp deployments.
- 2026-08-101.11.0 — Rich MojoSec evidence and explicit all-tier tests
Django-MOJO 1.11.0 restores trusted SSH and sudo attribution on current Amazon Linux, expands protected web and session evidence, and raises bounded package-change journal limits for large wheels. Test consumers must replace --full with --all to run opt-in tiers.
- 2026-08-101.10.2 — Framework upgrades handle duplicate package paths correctly
Django-MOJO 1.10.2 fixes a deployment check that counted the same package paths more than once and could incorrectly stop a framework upgrade.
- 2026-08-101.10.1 — Fleet deploys find application requirements reliably
Django-MOJO 1.10.1 fixes a fleet deployment failure where the protected dependency installer changed directories and could no longer find an application's requirements file. Canary deployments can now install dependencies from the configured project path and continue through their normal health-chec…
- 2026-08-101.10.0 — Built-in Admin control plane and durable platform operations
Django-MOJO 1.10 adds a workflow-centered Admin portal for people, WebApps, domains and DNS, activity, setup, and platform health, backed by resumable onboarding and UUID-owned deployment evidence. It also hardens fresh-auth boundaries, secret handling, and the first upgrade from 1.9.
- 2026-08-091.9.0 — GitHub-driven WebApp deploys, branded auth, and actionable MojoSec incidents
WebApp releases now deploy and prove convergence across the active Edge fleet directly from GitHub, with durable status and safe rollback. Hosted auth gains four responsive branded presets, while MojoSec incidents now carry validated source attribution and rich centrally scrubbed evidence.
- 2026-08-091.8.1 — Restarting nodes catch themselves up
A node whose job engine restarts — which every deploy causes — now reconciles itself the moment it comes back, instead of depending on a broadcast it may have been offline for or waiting out the ten-minute sweep. Built on a new engine startup-hook point any app can register on. Also adds a scoped pu…
- 2026-08-091.8.0 — Fleet-wide jobs actually reach the fleet, and web app releases can be published
Three fixes, all found publishing a real web app end to end for the first time. Two of them made the release plane unusable: no release could ever pass verification, and presigned uploads rejected any client that sent a Content-Type. The third is worse and older — work published to every runner on a…
- 2026-08-091.7.1 — Standard host integrity, and vhost naming without ceremony
Adds a standard AL2023 host-integrity profile — file-integrity monitoring, RPM verification, and exact trusted-change evidence — for nodes that opt in. Fixes two edge bugs: static assets under a declared app route 404ing, and renewed certificates silently not reaching nodes. Also removes the reserve…
- 2026-08-091.7.0 — MojoSec host sensor, and nodes that fetch their own releases
Adds MojoSec — a settings-free host sensor for dedicated EC2 nodes that turns journald, nginx and file-integrity signals into bounded batches for the incident system. Edge nodes now fetch promoted web app releases from S3 themselves, verified per file. Also fixes a bug that made every edge converge…
- 2026-08-081.6.0 — Vhost kinds, blocklists as data, packaged node plane
Vhosts are typed — api, site, site_api, redirect — each with its own template and knobs. IP and user-agent blocklists become rows you can watch before enforcing. The node-side tooling ships in the package. Contains two breaking changes: the vhost kind values, and the edge log location.
- 2026-08-071.5.0 — Fleet code deploy
A webhook on the deploy branch rolls the fleet: one canary node first, the rest released only once it proves the release, migrations behind a Postgres advisory lock. Adds `EDGE_CONVERGE_ENABLED` so the edge app can be installed for the deploy plane alone.
- 2026-08-071.4.0 — Redis index ownership, and file upload hardening
Closes a case where a test checkout could flush a Redis index another suite was using — including on a remote Redis, where the ownership guard was checking the wrong server entirely. Also hardens the file upload lifecycle and scopes record attachments.