Skip to main content

AxonFlow v11.5.0 Release Notes

v11.5.0 is a safe-off platform release. It adds the independently licensed payment_exception and support_refund module contracts and their governed execution foundations, and removes the golang.org/x/net HTML-parser denial-of-service (CVE-2026-78661) from every shipped binary, including the Prometheus and Grafana images, which are now built from pinned upstream source. Neither module is enabled by the release itself, and provider Send stays disabled.

What changed​

  • Independent commercial modules: payment_exception and support_refund are separately licensed, granted, metered and discoverable. A self-hosted Enterprise install activates a module only through the module-authority operator with a seller-signed deployment licence, an AxonFlow-signed distribution manifest and a customer-signed tenant grant; the dedicated deployment template and the install bundle now apply the module-authority schema for a selected module. Nothing is enabled by upgrading.
  • Governed model path: a subject-bound governed-model service adapter runs over the existing policy, budget, router, usage and attempt path. It accepts identity only through verified service delegation and rejects caller-selected routing controls.
  • Shared vocabulary and telemetry: non-entitling FinCrime protocol semantics and capability metadata carry explicit Enterprise ownership and a stable refusal vocabulary; documented dynamic outcome and administration paths are registered in the shared route-template vocabulary so telemetry persists bounded templates instead of concrete case identifiers.
  • Security: the shared Go networking modules, the gateway health-probe graph and the checksum-pinned MinIO/MC source builds move past CVE-2026-78661; Excelize moves to v2.11.1 (CVE-2026-107223). Prometheus is built from the pinned upstream 3.16.0 source commit and Grafana from upstream 13.3.1-slim with both data-source backends rebuilt from their pinned sources, each with golang.org/x/net at v0.62.0 proven on the binaries at build time, because no published tag of those components is free of the advisory.
  • Community: the Community agent and orchestrator receive the shared networking, vocabulary and governed-model changes; Community receives no FinCrime pack, scorer, grant, quota, model bundle, commercial outcome module or Square connector.

Deployment and migration​

The upgrade is additive. In-VPC Enterprise installs apply core migration 195 and Enterprise migrations 166–170 at Agent startup; a dedicated install that selects a commercial outcome module additionally applies the self-hosted module-authority schema (Community SaaS migrations 189, 191, 195 and 205–208) under the self-hosted-outcomes backend profile. Agent /health returns HTTP 503 until migrations and route registration finish. Retain the prior database snapshot as the rollback anchor; an image rollback does not reverse schema migrations.

The release images were built by a sealed multi-architecture pipeline from one source commit, scanned at HIGH and CRITICAL severity with zero findings on both architectures, and promoted by digest to both registries with identical digests. Use only the verified v11.5.0 digest set from your welcome bundle.

Client versions​

No SDK or plugin minimum floor changed in this platform release. This at-tag snapshot was frozen from public-registry and GitHub-release readbacks on 14 November 2026.

ClientVersionNotes
Python, TypeScript, Go, and Java SDKs9.5.1Unchanged; public before the platform tag.
Rust SDK (preview)0.12.1Unchanged.
OpenClaw plugin2.10.4Public; the platform recommendation is reconciled with the already-published artifact.
Claude Code plugin1.14.0Unchanged.
Cursor plugin1.10.0Unchanged.
Codex plugin1.10.0Unchanged.
Claude Desktop proxy0.4.1Unchanged.
n8n node1.2.1Unchanged; 1.3.0 is prepared but deferred until its runtime publication gate can run.
Google ADK plugin1.4.0Unchanged.
LiteLLM integration1.1.1Unchanged.

For versions available now, use the current client-version manifest and the installation pages. Later client patches must not rewrite this historical at-tag record.

Verify after upgrade​

Confirm Agent and Orchestrator report v11.5.0, service counts are healthy, no outcome module is active unless you installed one through the module-authority operator, and provider Send remains disabled. For a self-hosted module install, require the operator's completed authority verification and matching structured readback before treating the module as ready.

The Community source release targets the independently reviewed Community mirror of the tagged Enterprise source.