Skip to main content

AxonFlow v9.14.1 Release Notes

v9.14.1 is a patch release with one functional fix and a source-availability and licensing hygiene correction on the public community mirror. It carries one additive migration, no data mutation, and no behavior change for community binaries. It is a patch by the 2026-07-30 semver policy: no removed capability, no new required credential, no new refusal.

Am I affected?​

Deployments that export RBI compliance audits as PDF or XLSX get the fix below. If you export only JSON or CSV, or do not use the RBI module, this upgrade is routine.

Everyone else: this release changes nothing about how your binaries behave. The remaining changes are to what the public community repository publishes and how it is licensed, not to the running platform.

RBI audit export accepts PDF and XLSX​

v9.14.0 shipped an rbi_audit_exports.format CHECK constraint that admitted only json and csv, so a request for the PDF or XLSX artifact failed at persistence even though the report facade advertised those formats. Migration industry/banking/304 widens the constraint to include pdf and xlsx, matching what the facade offers. (#3269)

Enterprise-only source removed from the community distribution​

The compliance-reporting modules (RBI, SEBI, EU AI Act, MAS FEAT, OJK and the unified compliance-report facade) carry a //go:build enterprise tag in normally-named files. The community mirror sync excluded enterprise code by filename (*_enterprise.go), so these build-tagged files were published to the public repository even though they were never part of the community binary, which builds from the community stubs.

This release corrects that:

  • The sync now excludes enterprise code by build-tag content, and a fail-closed gate aborts the sync if any //go:build enterprise file would reach the mirror. (#3272)
  • The affected files' SPDX headers were corrected from Apache-2.0 to BUSL-1.1, and the files were purged from the mirror. (#3270)

There is no functional change: community binaries and their behavior are identical to v9.14.0.

Also in this release​

  • The last of the ee/platform/orchestrator/* compliance overlays are removed so fixes to those modules reach shipped binaries, and a build-time guard fails the build if an overlay is reintroduced. (#3269)
  • The compliance-facade route-drift guard was split across the edition build-tag axis so the community mirror build stays green after the purge. (#3273)

Before you upgrade​

Apply migration industry/banking/304 (additive; widens a CHECK constraint). There are no other migrations, no data mutation, and no configuration changes. Community deployments need do nothing beyond the routine image pull.

SDK and plugin compatibility​

No SDK or plugin changes. Clients compatible with v9.14.0 are compatible with v9.14.1.

Last updated on