Release Date: 2 June 2026

Release (1.2.0)

Overview

This release prepares for future capabilities for self-managed Community Edition instances to be migrated to Neo4j Aura. It also includes reliability and performance improvements for clustered deployments.

Features

• Community Edition migration to Aura (when enabled in Fleet Management).
  • The plugin includes support to dump a local database, upload it to Aura, and report migration step status (dump, upload, import) back to Fleet Management.
  • Store size and resource metrics are collected from Community Edition instances to support sizing.
  • This capability will be available in Fleet Manager once the migration feature is released.

Fixes

• Fix for cluster token rotation handling that could affect Fleet Management connectivity on clustered deployments.
• Improved handling when the Fleet Management API is unreachable, including clearer error messages and more reliable reachability checks.
• Improved Fleet Management lifecycle and connection state handling after API errors.
• Fix for a null pointer exception when applying configuration updates from the server.
• Fix for ping endpoint response handling when configuration is delivered with other report responses.
• Reduced overhead from Fleet Management internal queries on the database (fewer repeated SHOW DATABASES and license checks).
• Fix for transaction and result-set resource handling that could affect stability under load.

Deprecation

Notice: Fleet Manager is available as part of the Neo4j database from release 2026.03. If running this version or later the plugin installation is no longer required and the plugin should be removed.