chore(deps): Upgrade Neo4j to 2026.04.0

[fatih-acar]

Summary

Upgrades Neo4j from 2025.10.1 to 2026.04.0 (latest calver release).

Version Changes

Component	Previous	New
Neo4j (docker)	neo4j:2025.10.1-{community,enterprise}	neo4j:2026.04.0-{community,enterprise}
Neo4j Helm chart	2025.10.1-4	2026.4.0

Release-notes review (2025.11 → 2026.04)

Six calver releases reviewed. Summary of relevant items:

• 2025.11.2 — Cypher 25 collection functions added (additive). Dynamic-label + composite-index bug fixed in 2026.01.4 (Infrahub does not use dynamic labels — not affected).
• 2025.12.1 — Wildcard support for allowed/denied database names; path-value comparison perf improvements. No code impact.
• 2026.02.3 — Security patches (Jackson, Jetty 12.0.33). Pipelined-runtime bug fix for some EXISTS subqueries.
• 2026.03.1 — New ACYCLIC path mode and PROPERTY_EXISTS() (additive). X-Forwarded-Host headers headed for default-disable in a future release (not used here).
• 2026.04.0 — New IS [NOT] LABELED predicate and FOR statement (additive, GQL alignment). New opt-in server.memory.pagecache.async setting. Bundled Fleet Management removed (not used).

No breaking Cypher syntax changes. No removed features that Infrahub uses. No driver-pin requirement.

Code Changes Beyond Version Bumps

None required. The repo already uses modern Cypher (elementId, FOR (n:L), CALL (var) { … } IN TRANSACTIONS, IS :: type predicates), and the SHOW INDEXES/SHOW CONSTRAINTS column schema is stable across the upgrade range.

Files Updated

• backend/tests/helpers/constants.py
• docker-compose.yml
• tasks/shared.py
• .github/workflows/version-upgrade.yml
• python_testcontainers/infrahub_testcontainers/container.py
• python_testcontainers/infrahub_testcontainers/docker-compose.test.yml
• python_testcontainers/infrahub_testcontainers/docker-compose-cluster.test.yml (3 occurrences)
• utilities/db_backup/__main__.py
• docs/docs/development-resources/local-demo-environment.mdx
• docs/docs/deploy-manage/install-configure/production-deployment/high-availability.mdx (4 Helm-chart version refs)
• changelog/+upgrade-neo4j-2026-04.housekeeping.md (new)

Release Notes

• Neo4j 2026.04.0
• Neo4j 2026.03.1
• Neo4j 2026.02.3
• Neo4j 2025.12.1
• Neo4j 2025.11.2

Test plan

• CI passes all tests
• Local docker-compose starts successfully
• Integration tests pass
• No performance regression when running infrahub-private-tests (scale tests)
• Migration and auto-upgrade of persistent containers pass (version-upgrade job succeeds)
• Helm chart 2026.4.0 has been tested with upgraded dependencies
• Deployment examples have been updated

---

Summary by cubic

Upgrade Neo4j to 2026.04.0 across Docker, Helm, CI/test, backup tooling, and docs. Security and Cypher updates; no breaking changes; no app code changes.

• Dependencies
  • Docker images: neo4j:2025.10.1-{community,enterprise} → neo4j:2026.04.0-{community,enterprise}
  • Helm chart: 2025.10.1-4 → 2026.4.0
  • Version-upgrade workflow now uses neo4j:2026.04.0-enterprise

^{Written for commit d6066c3. Summary will update on new commits. Review in cubic}

[cubic-dev-ai]

No issues found across 147 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Note: This PR contains a large number of files. cubic only reviews up to 100 files per PR, so some files may not have been reviewed. cubic prioritizes the most important files to review.
On a pro plan you can use ultrareview for larger PRs.
Shadow auto-approve: would require human review. This PR updates a critical production dependency (Neo4j database) and, per policy, dependency version bumps, especially for core infrastructure, require human review to verify compatibility and ensure the test plan is validated.

Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="changelog/+upgrade-neo4j-2026-04.housekeeping.md">

<violation number="1" location="changelog/+upgrade-neo4j-2026-04.housekeeping.md:1">
P3: Typo: 'Upgradedd' should be 'Upgraded'.</violation>
</file>

<sub>Shadow auto-approve: would not auto-approve because issues were found.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Typo: 'Upgradedd' should be 'Upgraded'.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At changelog/+upgrade-neo4j-2026-04.housekeeping.md, line 1:

<comment>Typo: 'Upgradedd' should be 'Upgraded'.</comment>

<file context>
@@ -1 +1 @@
-Upgraded Neo4j from `2025.10.1` to `2026.04.0`.
+Upgradedd Neo4j from `2025.10.1` to `2026.04.0`.
</file context>

Suggested change

	Upgradedd Neo4j from `2025.10.1` to `2026.04.0`.
	Upgraded Neo4j from `2025.10.1` to `2026.04.0`.

[codspeed-hq]

Merging this PR will not alter performance

✅ 12 untouched benchmarks

---

_{Comparing fac-upgrade-neo4j-2026 (d6066c3) with stable (e3b9f4d)}