Neo4j
Home
Feedback
Changelog

Changelog

Follow up on the latest improvements and updates.

RSS

new

improved

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database March Release Update

The Neo4j Aura March release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later.
Some highlights include:
  • dbms.components() will return ‘5.27.0’ in the column versions. This is to support existing client applications that rely on the previous version format.
  • When dbms.cypher.lenient_create_relationship is set to true, MERGE clauses will not fail with Neo.TransientError.Transaction.Outdated.
  • Includes a new error handling mode for CALL IN TRANSACTIONS: ON ERROR RETRY.
Fixes
  • Fixes a bug with relationship traversal cursor pooling that could cause an ExpandInto operator to generate an incorrect relationship match in certain rare queries when executing on a block format database.
  • Fixes a issue where X1 page does not exist for node -1 errors appearing after node deletion.
  • Fixes a issue where …DELETE n RETURN n could fail in some scenarios.
  • Fixes a issue where we returned true instead of the actual property value for some specific WHERE clauses.
  • Fixes a issue where serialization of an empty list inside another list would cause an index out of bounds exception.
  • Fixes a bug with Dynamic Relationship Types where the first type would be inadvertently cached and reused for all rows.
Please refer to the Aura Release Notes for more information on any of the changes.

new

improved

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database February 2025 Release Update

The Neo4j Aura February release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later.
Some highlights include:
  • dbms.components() will return ‘5.27-aura’ in the column versions to maintain compatibility with existing client applications.
  • Optimized memory consumption for eagerness analysis in Cypher when handling unions.
  • Status descriptions for notifications now include the database name for unrecognized labels (01N50), relationship types (01N51), and properties (01N52).
  • NotSystemDatabaseException is now split into two exceptions:
    NotSystemDatabaseException
    , which is thrown when system-only queries are run on a non-system database, and
    DisallowedOnSystemException
    , which is thrown when non-system queries are run on the system database.
Fixes
  • Server: Resolved an issue with populating multiple index types on the same schema from concurrent transactions.
  • Cypher: Fixed java.lang.NoSuchFieldError: v0_tokenManager error when returning full nodes or relationships in some queries.
Please refer to the Aura Release Notes for more information on any of the changes.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database January 2025 Release Update

The Neo4j Aura January release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later. This is our first release using our new Calendar Version scheme.
Some highlights include:
  • Index Creation: Default index provider is now always used, as index providers no longer control index behavior (since version 5.0).
  • Protocol Update: Introduced Bolt 5.8.
Fixes
  • Resolved double-indexing of dense relationships, detectable during consistency checks.
  • Fixed issues with removing the last indexed property from dense relationships, which could fail during recovery or clustering.
  • Addressed transaction safety in DDL operations.
  • Corrected warnings related to Java Compressed Object Pointers in 32-48GB heaps.
  • Fixed a collect function bug that failed to preserve order in specific cases under parallel runtime.
Please refer to the Aura Release notes for more information on the changes.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Aura API rate limiting January update - extension

On 4 December 2024 we advised everyone that, starting 27 Jan 2025, we will adjust the rate limiting for the Aura API /oauth/token endpoint, which is used to obtain authorization tokens.
We will be delaying this change to ensure that all Aura API users have sufficient time to implement the necessary updates. We will contacting users ahead of time to confirm details and also communicating here too.
Since each authorization token remains valid for one hour, we recommend optimizing your API usage by following these steps:
  • Retrieve the token once per hour: As tokens remain valid for an hour, reduce the frequency of token requests and reuse the same token for multiple API calls.
  • Implement token caching: Store the token securely within your system to reuse it for subsequent requests during its validity period, minimizing unnecessary calls to the endpoint.
If you need additional guidance or help, please reach out to Neo4j Aura Support. Our priority is to ensure fair and equitable access to our APIs for all customers.
Rate limiting for other API endpoints will remain unchanged at this time.
Thank you,
The Aura Team

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Important Update: Calendar Versioning & Cypher 25

Calendar Versioning
Starting in January 2025, Neo4j is adopting a calendar-based versioning format (e.g., 2025.01), replacing traditional semantic versioning after the release of version 5 LTS. As an Aura customer, you’re already automatically on the latest version, and will now see the latest Calendar version in your database details. No action is required as a result of this message.
There is no change for customers using version 4; however, we advise migrating to the latest version to take advantage of great new features, such as Parallel Runtime for 10x faster query performance, Block Format, Differential Backups, and more.
Cypher 5 and Cypher 25: More Choice, Same Simplicity
When an Aura instance is upgraded to the latest version, Cypher Language Version 5, the Cypher Language in Neo4j 5.x, remains the default. When Cypher Version 25 is released this year, it will be available in all database instances on the latest release. All Aura customers on latest Calendar Version will be able to optionally:
  • Choose between Cypher 5 or Cypher 25 for queries, regardless of the database version.
  • Explore new Cypher features without altering your existing applications.
  • Change the default version of Cypher for the database.
The Cypher API compatibility layer ensures seamless transitions and lets you adopt new capabilities at your pace.
These enhancements will roll out soon, keeping Aura at the forefront of graph database technology.
Thank you
The Neo4j Team
FAQ
What is calendar-based versioning, and why is it being introduced?
Calendar-based versioning replaces traditional semantic versioning. Future Neo4j releases will follow the format of YYYY.MM.Patch (e.g., 2025.01.00). This approach simplifies how Aura handles Fully Managed upgrades, ensuring frequent access to new features, and eliminating the need for disruptive major version migrations. More details on why calendar-based versioning is being introduced are provided in the blog post, Neo4j Takes the Lead: Transforming Graph Database Management With Cypher API Versioning and Database Calendar Versioning.
Are there any changes to how upgrades work?
No. Aura does not have any scheduled maintenance windows. It is designed to be always on and available, with all corrections, fixes, and upgrades automatically applied in the background.
Releases for the Neo4j database are also deployed when they become available. Operations are non-disruptive, and you shouldn’t experience any downtime as a result.
Will this change impact me as an Aura API user?
The Aura API will continue to accept version 5 requests. Requests using version 5 will create instances with the Latest Calendar Version.
What about deprecation of features?
Neo4j has a customer-focused deprecation policy: Features will only be deprecated if an alternative is available. Deprecated features remain supported with at least 12 months’ notice before removal.
How will the Cypher API compatibility layer help?
The compatibility layer allows you to specify the default Cypher version for your database or individual queries. This ensures that adopting new Cypher versions like 25 can happen gradually, without disrupting existing applications or workflows.
Do I need to migrate my queries from Cypher 5 to Cypher 25?
Eventually, but Cypher 5 will be supported unchanged (apart from resolving defects and security issues) for several years. We are committed to at least a year's notice before any withdrawal of a Cypher version. Cypher 25 starts as a copy of Cypher 5, with some deprecated features removed. It will then get additive features in the coming years.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Adaptive Email MFA enabled for all Aura customers

We’re pleased to introduce Adaptive Email MFA—a new security feature designed to enhance account protection across all Neo4j Aura tiers (Free, Professional, Business Critical, and Virtual Dedicated Cloud). Adaptive MFA challenges you with a second factor of authentication only when it detects unusual sign-in activity, ensuring a more seamless experience without compromising on security.
Key Benefits
  • Increased Baseline Security:
    Adaptive MFA continuously evaluates the risk of login attempts, providing an additional layer of protection against unauthorized access.
  • Reduced MFA Prompts:
    For day-to-day logins from familiar devices and locations, you’ll see fewer MFA challenges, resulting in a smoother login process.
  • Applies to All Aura Tiers:
    This improvement benefits every Aura user, maintaining a consistent level of security across all service levels.
How Adaptive MFA Works
Adaptive MFA monitors multiple factors to determine if a login attempt warrants an MFA challenge, some of which include:
  1. New Device:
    If you log in using a device you haven’t used in the last 30 days, the system lowers its confidence score and triggers an MFA prompt.
  2. Impossible Travel:
    If your login location changes so drastically that it suggests “impossible travel” (beyond what’s realistically achievable), an MFA prompt is triggered.
  3. Untrusted IP:
    If your IP address is flagged as untrustworthy, you’ll be asked to complete an MFA challenge.
Who Is Affected
Adaptive MFA applies to all users who log in to Neo4j Aura with a username and password. If you typically access Aura from the same device, browser, and location, you’ll rarely encounter additional MFA challenges.
No Action Required
This feature is non-disruptive and will be enabled automatically. Users do not need to take any steps to benefit from enhanced security and a more convenient login experience.
For more information or assistance, please contact our support team. We’re committed to keeping your Neo4j Aura environment secure and easy to use.

new

improved

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Aura CLI - open beta

I’m pleased to announce the open beta for the new, Go-based Aura CLI.
You can find it here: https://github.com/neo4j/cli/releases, with native binaries available for all major platforms.
Feedback is welcome via the GitHub issue page here: https://github.com/neo4j/cli/issues.
The Aura CLI will replace the Labs Aura CLI and offers equivalent functionality, with the addition of commands for customer-managed keys (CMK).
The open beta will run for a short period before GA at the end of December 2024. At that time, the Labs Aura CLI will become read-only and marked as deprecated. It will still be installable and usable, but you are advised to transition to the new Aura CLI.
Thank you, and I look forward to your feedback!
Jonathan Giffard
PM, Drivers, CLI, GraphQL & Query API

new

AuraDS Enterprise

AuraDS Enterprise: On-demand Snapshot retention update

We are updating all AuraDS Enterprise users about an upcoming change to the snapshot retention policy for Neo4j AuraDS Enterprise instances.
Effective from
13 January 2025
onwards, new and existing user-initiated ‘on-demand’ snapshots will now be retained for
90 days
from the date of creation.
What is a Neo4j AuraDS snapshot?
A snapshot is a copy of the data in your instance at a specific point in time. They are listed in the
Snapshots
tab of the AuraDS Enterprise instance. Neo4j regularly takes snapshots of your AuraDS Enterprise instance, and you can request a snapshot to be taken on-demand.
What is changing?
We currently retain AuraDS Enterprise user-initiated 'on-demand' snapshots for 180 days. From after 13 January 2025 we will retain these for 90 days, and this will be applicable for both newly created and existing user-initiated snapshots.
Why is it changing?
To better align with AuraDB and ensure consistency across our Aura Tiers, we are refining our backup retention policy to establish a standard approach.
Will there be any changes to scheduled snapshots?
The retention period for scheduled snapshots is currently 14 days and will remain unchanged at this time.
Who can I contact for more information?
If you have any further questions, please don’t hesitate to reach out to our support team.
Thanks
The Aura Team

new

Advanced Warning Aura Platform

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Aura API rate limiting update!

We currently set a global rate limit of
125 requests per minute
per client ID for all Aura API endpoints.
Starting 27 Jan 2025, we will adjust the rate limiting for the Aura API /oauth/token endpoint, which is used to obtain authorization tokens. The new limit will be set to
15 requests per hour
.
Since each authorization token remains valid for one hour, we recommend optimizing your API usage in advance by following these steps:
  1. Retrieve the token once per hour
    : As tokens remain valid for an hour, reduce the frequency of token requests and reuse the same token for multiple API calls.
  2. Implement token caching
    : Store the token securely within your system to reuse it for subsequent requests during its validity period, minimizing unnecessary calls to the endpoint.
If you need additional guidance or help, please reach out to Neo4j Aura Support. Our priority is to ensure fair and equitable access to our APIs for all customers.
We will provide confirmation of this update in January, along with a link to the relevant documentation. Rate limiting for other endpoints will remain unchanged at this time.
Thank you,
The Aura Team

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database December release update!

The latest Neo4j Aura Database release has started to roll out, beginning on AuraDB Free, then progressing to higher tiers from later this week.
Updates include:
Language
  • Added support for dynamic expressions in
    CREATE
    ,
    MATCH
    , and
    MERGE
    .
  • Enabled dynamic CSV column referencing in
    LOAD CSV
    .
  • Deprecated HTTP API; use Query API for executing Cypher statements.
Fixes
  • Kernel: Fixed issues with dense relationship property removal during recovery.
  • Cypher: Fixed missing nodes in queries with indexes and null properties.
  • Cypher: Resolved errors: key not found: VariableSlotKey and Type mismatch.
Full details of updates and fixes are available in the Neo4j Aura Release Notes
Load More
→