Release v0.11.1 · admina-org/admina

[0.11.1] — 2026-07-16

Patch release: dependency security updates, an information-disclosure fix,
and two configuration/tooling corrections. No API changes.

API responses no longer carry exception text. The dashboard services
endpoint returned str(exc) from failed Redis and ClickHouse health
checks, and POST /api/v1/validate returned the raw exception text of a
guard that broke its contract. Either could echo a host, port or a
credential embedded in a connection URL back to the caller. Both now
report a generic reason; the detail is logged server-side and the
forensic records keep the full text, so the audit trail is unchanged.
cryptography updated to 50.0.0, resolving the high-severity advisory
affecting < 50.0.0. The dependency ceiling is widened from <50 to
<51.
setuptools updated to 83.0.0 and pymdown-extensions to 11.0.1,
resolving two moderate advisories reported against the lockfile.

ADMINA_GOVERNANCE_MODE is now honoured. The proxy Settings field
declared no alias, so pydantic bound it to the bare name GOVERNANCE_MODE
and — because the model is configured with extra="ignore" — the
prefixed variable was silently discarded with no error, despite being the
name advertised by the field's own comment, admina.yaml.example,
admina doctor, and the dashboard. It now declares
validation_alias="ADMINA_GOVERNANCE_MODE", matching the
ADMINA_GUARD_FAIL_MODE precedent. Note: the undocumented bare
GOVERNANCE_MODE variable is no longer accepted; a deployment relying on
it silently reverts to the enforce default, so switch it to the prefixed
name. The bare LOOP_* and INJECTION_* variables are unaffected — those
are read directly from the environment by admina/core/config.py and stay
unprefixed.
make status and scripts/generate_docs.py referenced top-level
proxy/, domains/, sdk/, core/ and plugins/ directories that have
not existed since the package was consolidated under admina/. Both now
use the real paths, and engine_status is imported from admina.engines.