Release Notes

This section documents the version history of the Mango platform by Radix IoT, including detailed changelogs, major feature highlights, and upgrade guidance for administrators planning version transitions.

Versioning Model

Starting with Mango 5.0, Radix IoT adopted a unified versioning system. Under this model, every release ships the core platform and all official modules together as a single versioned bundle. When any component receives an update, whether it is the core runtime, a data source module, or a UI enhancement, the entire platform is released as a new version. For example, if the Watchlist module receives a patch, the full bundle is released as the next incremental version (e.g., 5.0.1).

Version numbers follow semantic versioning conventions:

• Major versions (e.g., 5.0.0) introduce significant architectural changes, new features, or breaking changes that may require migration steps. A new license is typically required when upgrading across major versions.
• Minor versions (e.g., 5.5.0) add new features, module enhancements, and library upgrades while maintaining backward compatibility within the major release line.
• Patch versions (e.g., 5.5.7) contain bug fixes, security patches, and stability improvements with no breaking changes.

Java Runtime Requirements

Each major version of Mango specifies minimum and recommended Java versions:

Mango Version	Minimum Java	Recommended Java	Build Java
5.0.x -- 5.3.x	Java 17	Java 17	Java 17
5.4.x -- 5.5.x	Java 17	Java 21	Java 21+
5.6.x	Java 17	Java 21	Java 25
5.7.x	Java 17	Java 21	Java 25

Radix IoT recommends the Azul Zulu builds of OpenJDK, though any compliant OpenJDK distribution is supported.

Upgrade Path Recommendations

When planning an upgrade, keep these guidelines in mind:

• Always back up your database and configuration before upgrading. Test the upgrade in a non-production environment first.
• Upgrade within a major version by applying the latest patch release. These are designed to be drop-in replacements with no migration steps.
• Upgrade across major versions by following the dedicated upgrade guide. Major version upgrades may require a new license, Java version changes, and database migrations.
• Review the release notes for every version between your current version and your target version to identify any breaking changes, deprecated features, or required configuration updates.

Build Reports for Each Release

Every released version publishes a set of build reports alongside the Mango source at radixiot.github.io/mango-code-site. Pick a version from the sidebar there to open its reports. Coverage starts at 5.4.0.

Report	What it's for	Path within a version
Swagger	Browse every REST endpoint and its request/response schemas.	restapi/swagger.html
Redoc	The same endpoints in a three-column reading layout.	restapi/redoc.html
OpenAPI Definition	The raw spec, for generating clients or diffing endpoints between versions.	restapi/openapi.json restapi/openapi.yaml
Third Parties	Every bundled library and its license. Answers "what ships inside Mango 5.7.5?" for security and compliance reviews.	third-party-report.html aggregate-third-party-report.html
Dependency Convergence	Resolved dependency versions for that build, including transitive ones.	dependency-convergence.html dependency-management.html
Project metadata	Licenses, Maven coordinates, the module list, and build plugins.	licenses.html dependency-info.html modules.html plugins.html

Append the path to the version root. For example, the Redoc view and the third-party license report for 5.7.5 are:

https://radixiot.github.io/mango-code-site/5.7.5/restapi/redoc.html
https://radixiot.github.io/mango-code-site/5.7.5/third-party-report.html

The Swagger entry point is the exception — it has its own version dropdown, so one link covers every release.

These reports are generated from the build itself, so they are authoritative for a given version in a way that hand-written release notes can't be — reach for them when you need to confirm exactly which library version a release shipped.

Software Bill of Materials

Starting in Mango 5.6.11 and 5.7.5, every release also publishes a CycloneDX software bill of materials. A signed <artifactId>-<version>-cyclonedx.json file sits alongside the core bundle and alongside each module, listing exactly the third-party Java components that artifact ships. This is the machine-readable counterpart to the Third Parties report above — prefer it for automated compliance and vulnerability tooling. The npm packages bundled into the web UI are not yet covered.

All supported release lines are also scanned nightly against the OSV vulnerability database for known vulnerabilities in their third-party dependencies, direct and transitive. Findings are triaged into dependency updates — which ship in patch releases and are listed under core in the release notes — or documented accepted risks.

note

The report sidebar on that site also lists a Javadoc entry, but the Java API docs are not currently published — the link returns a 404 for every version.

In This Section

Page	Description
v5 Release Notes	Index of all Mango 5.x release series with links to per-series changelogs.
Mango 5.7.x	Changelog for the 5.7.x series — Spring 7 / Jetty EE11 upgrade, BACnet4J reliability fixes, translation overrides.
Mango 5.6.x	Changelog for the 5.6.x series — Java 25 support, Prometheus metrics, offline gRPC queuing, email escalation levels.
Mango 5.5.x	Changelog for the 5.5.x series — database connection pooling, maintenance events redesign, MQTT publisher.
Mango 5.4.x	Changelog for the 5.4.x series — OpenAPI 3.1 docs, H2 auto-upgrade, JSON config import on startup.
Mango 5.3.x	Changelog for the 5.3.x series — Docker non-root user, gRPC-Web proxy, read replica SQL support.
Mango 5.2.x	Changelog for the 5.2.x series — OAuth 2.0 resource server, PostgreSQL backup/restore, security hardening.
Mango 5.1.x	Changelog for the 5.1.x series — MQTT publisher, Maintenance Events redesign, PKI certificate UI.
Mango 5.0.x	Changelog for the initial 5.0.x series — Java 17 required, HTTPS by default, gRPC server, unified versioning.
Mango v5 Highlights	Overview of the major features introduced in Mango 5.0, including PostgreSQL support, the Pi-Portfolio Manager (EMS), gRPC publisher, HTTPS by default, PKI services, and the redesigned UI.
Upgrade to v5	Step-by-step instructions for upgrading from Mango 4.x to Mango 5.x, including Java requirements, license information, and browser cache considerations.