Getting started: Release notes

Release Date: 2025-10-09

(v4.2.5) Google Spanner Graph: Add official support, improve full-text search and schema administration
(v4.2.5) License: License details are now visible in the license page
(v4.2.5) Documentation: Clarify the impact of the automatic coloring for multi-category nodes
(v4.2.5) Landing Page: add suggested actions
(v4.2.4) Data Model: New feature allowing users to discover the graph data model
(v4.2.4) Google Spanner Graph: Allow administrators to configure a new data-source from the user-interface
(v4.2.4) Documentation: Describe the environment variables that can be used when deploying
(v4.2.4) Documentation: Improve the instructions of the Neo4j block storage migration script
(v4.2.4) Security: Update Node.js to v22.19.0
(v4.2.3) Alerts: Allow deleting cases in the case list (including in bulk)
(v4.2.3) Alerts: Improved filtering, sorting and selecting cases in the case list
(v4.2.3) Configuration Migration Plugin: Remove the need to use a service account
(v4.2.3) Neo4j: New script to help migrate to block storage
(v4.2.3) No-Code Query Builder: Add explanations for the "provide value on-demand" feature
(v4.2.3) Security: Updated Node.js to v22.17.1
(v4.2.2) Alerts: Make some visualization features available in the case view (design panel, graph edition, quick actions, search bar)
(v4.2.2) Entity Resolution: Performance improvements
(v4.2.2) Access Linkurious Enterprise Public Roadmap
(v4.2.2) Alerts: Change the updatedAt behavior
(v4.2.2) Amazon Neptune: Document the full-text search option and their limitations
(v4.2.2) Promote Entity Resolution to Stable
(v4.2.2) Queries: Remove toaster for query results confirmation
(v4.2.1) Amazon Neptune: add support for OpenSearch 2.x
(v4.2.1) Deployment: new cluster mode for fault tolerance
(v4.2.1) Entity Resolution: various user experience, performance and stability improvements
(v4.2.1) Node grouping: node groups can be collapsed and expanded to simplify the visualization
(v4.2.1) Query Builder: new cardinality filters on traversals, improved handling of slow queries
(v4.2.1) Configuration: Automatically migrate legacy Azure SSO OAuth URLs
(v4.2.1) Documentation: explain the order in which styles rules are applied
(v4.2.1) Security: Update Node.js to v22.15.1
(v4.2.0) Security: Update to Node.js v22
(v4.2.0) Embedded Elasticsearch: Update to Elasticsearch 8.17.4
(v4.2.0) Memgraph: Add support for Memgraph 3.1
(v4.2.0) Neo4j: Add support for Neo4j 2025.03
(v4.2.0) Security: Enforce the cookie secret configuration to cryptographically secure
(v4.2.0) User-data store: Add support for MariaDB 11.4
(v4.2.0) User-data store: Add support for MySQL 8.4

(v4.2.5) Alerts: Fixed dynamic filters in the case list on MSSQL
(v4.2.5) Google Spanner Graph: Loading a visualization with more than 200 nodes fails frequently
(v4.2.5) Landing Page: Thumbnails are not available right after saving a visualization for the first time
(v4.2.5) No-Code Query Builder: The lists of node categories and edge-types are no longer filtered according to selected context with Neo4
(v4.2.5) Node grouping: Collapsed node group styles are no longer refreshed automatically
(v4.2.5) Users & Groups: Group identifier are not longer visible in the interface
(v4.2.5) Users & Groups: Misleading data about the groups a user belongs is displayed when filtering users by group
(v4.2.5) Visualization: After running a query, the filter panel shows inconsistent information
(v4.2.5) Visualization: he edit-lock is no longer automatically released after the visualization is closed
(v4.2.5) Visualization: It is no longer possible to remove a node from the selection
(v4.2.5) Visualization: The order of selected nodes is not taken into account when running a query or creating an edge
(v4.2.4) Alerts: Error when working with more than 40 columns in the case list
(v4.2.4) Alerts: The case list order is not properly applied when a custom column order is applied
(v4.2.4) Alerts: When multiple models match the exact same elements, they are not accounted for properly
(v4.2.4) Case Management: User avatar colors differ in various places
(v4.2.4) Data Export: Error while exporting an unsaved visualizations
(v4.2.4) Data-source settings: Configuring an incompatible index vendor causes the server to crash
(v4.2.4) Documentation: The steps to start on macOS do not allow to start Elasticsearch on recent versions of macOS
(v4.2.4) Google Spanner Graph: Detecting the type of a key property can fail when property aliases are used
(v4.2.4) Image Export: Node badges are displayed twice
(v4.2.4) Neo4j: The block storage migration script alters the "last modified date" of visualizations and cases
(v4.2.4) Neo4j: The block storage migration script does not migrate the IDs of missing graph elements
(v4.2.4) Neo4j: The block storage migration script sometimes crashes on MariaDB/MySQL/MSSQL
(v4.2.4) Node Grouping: The "center visualization" button does not work on a node belonging to a collapsed node group
(v4.2.3) Deployment: On macOS, running the "xattr" command on the data folder can fail
(v4.2.3) Documentation: Missing step in the configuration of the redirect url in Azure Active Directory
(v4.2.3) Entity Resolution: The "new" tag is not properly aligned
(v4.2.3) Entity Resolution: Wrong text in the screen
(v4.2.3) Google Spanner Graph: A valid query (or attribute query) with template fields is sometimes detected as invalid
(v4.2.3) Google Spanner Graph: When table aliases are used in the graph schema, some edges are missing from the graph
(v4.2.3) Neo4j: Connecting to Neo4j Aura Pro fails with an access error
(v4.2.3) Visualization: In the multi-node selection panel, the sorting order for properties of type "currency" is incorrect
(v4.2.2) Case view: Can't run queries requiring user input anymore
(v4.2.2) Case View: Dismissing the "Save before exit" popin leads to leave the case
(v4.2.2) Entity Resolution: Database connection issues causing "why entity" to crash
(v4.2.2) Entity Resolution: ServiceApiKey is not obfuscated in the configuration page
(v4.2.2) Error when using rgba syntax for colors in the default styles
(v4.2.2) In some cases the UI is not accessible after a datasource disconnects
(v4.2.2) Multi-selection panel: Properties named id or caption are not always correctly displayed
(v4.2.2) Query Builder: Copy fix for estimated results
(v4.2.2) Server: Manager fails to start on VMs
(v4.2.2) Timeline: Counter of Visible entities is incorrect on Memgraph and Neptune with datetime properties
(v4.2.1) Authentication: error when the optional tenantID field is omitted from the Azure SSO configuration
(v4.2.1) Configuration-Migration Plugin: the migration fails for some node-grouping rules
(v4.2.1) Data-source: a graph database rebuild is not detected if the data-source is connected
(v4.2.1) Data-Table plugin: the plugin crashes when the graph query fails with an 500 error
(v4.2.1) Deployment: sometimes, the server fails to start and the error is not logged
(v4.2.1) Neo4j: failure to reconnect to a Neo4j cluster after the main Neo4j node goes offline
(v4.2.1) Queries: no message in the query panel when there are no queries to display
(v4.2.1) Queries: when a query returns more nodes than allowed, the truncated graph is displayed before the user dismisses the warning
(v4.2.1) Visualization: in the multi-selection table, the currency format is not applied for properties with a whitespace in their name
(v4.2.1) Visualization: when using the radial layout, removing the root node sometimes causes an error
(v4.2.1) Workspace: setting the visualization text background to null prevents adding new edges

(v4.2.1) If you are using the "fault tolerance" setup documented in previous version of the product, there are no breaking changes but it is strongly recommended to use the new cluster mode instead. The cluster mode has better cross-instance consistency guarantees, and makes it easier to configure the primary and secondary server instance correctly. For details, see https://doc.linkurious.com/admin-manual/4.2/cluster-mode/
(v4.2.1) If you are using Entity Resolution, you must update the Entity Resolution server to v1.1.0 and clear all records after updating to this version.
(v4.2.0) Configuration files with secrets encoded before Linkurious Enterprise v4.0.25 can no longer be decrypted. To avoid any issue, Linkurious must be updated to v4.1 before updating to v4.2.0, so that secrets in configuration files are migrated.
(v4.2.0) After this update, users using the embedded Elasticsearch must re-index their data-source.
(v4.2.0) If your configuration contains a server.cookieSecret value that is shorter than 64 characters, you must replace it with a longer value.

Previous Next

Getting started: Release notes

Changelog for Linkurious Enterprise v4.2.5

New Features & Improvements (37)

Bug Fixes (53)

Breaking changes (5)