Bump Neo4j 5.26 -> 2025.04

[CarsonF]

Obviously, they have a new versioning schema, but this is not treated as a major.

It appears that 5.26.6 (released 2025-05-06, two days before this commit) has a regression with optional match clauses.
This upgrade is a hope to fix that.

Superceeds #3418, hopefully.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Neo4j Docker image version was updated from 5.26-enterprise to 2025.04-enterprise in both the GitHub Actions workflow and the Docker Compose configuration. No other changes were made to service configurations, environment variables, or workflow steps.

Changes

File(s)	Change Summary
.github/workflows/test.yml	Updated Neo4j Docker image version in E2E test job.
docker-compose.yml	Updated Neo4j Docker image version for the db service.

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42d326f and 97f0e19.

📒 Files selected for processing (2)

• .github/workflows/test.yml (1 hunks)
• docker-compose.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (12)

• GitHub Check: E2E Tests (neo4j 6/6)
• GitHub Check: E2E Tests (neo4j 5/6)
• GitHub Check: E2E Tests (neo4j 4/6)
• GitHub Check: E2E Tests (neo4j 3/6)
• GitHub Check: E2E Tests (neo4j 2/6)
• GitHub Check: Generate (head)
• GitHub Check: E2E Tests (neo4j 1/6)
• GitHub Check: Clean
• GitHub Check: lint
• GitHub Check: Generate (base)
• GitHub Check: Unit
• GitHub Check: Analyze (javascript)

🔇 Additional comments (2)

docker-compose.yml (1)

3-3: Bump Neo4j Docker image version
Updated the db service image to neo4j:2025.04-enterprise to pull in the fix for the optional match regression introduced in 5.26.6.

.github/workflows/test.yml (1)

30-30: Update E2E test Neo4j image to 2025.04
Aligned the workflow’s Neo4j service image tag with the docker-compose.yml bump, ensuring CI runs against the patched release.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.