[fatih-acar]

Merge timing — resolved

This PR originally had to wait for the Infrahub 1.11 release, because Neo4j 2026.05 is validated against the Neo4j Python driver 6.2 and only 1.11 carries that driver.

Infrahub 1.11.0 has since shipped (infrahub-v1.11.0, 2026-08-19), and this branch now bumps appVersion to 1.11.0 alongside the Neo4j upgrade. The driver/server pairing is correct within this PR, so there is no longer an ordering constraint on the merge.

Summary

Brings the bundled Neo4j up to the version Infrahub is actually tested against. The neo4j subchart moves from 2025.10.1-4 to 2026.5.0, which deploys Neo4j 2026.05.0 — matching release-1.11 in the infrahub repo.

This tracks the upstream bump in opsmill/infrahub@ad08b81a7 ("chore: upgrade to Python 3.14 with Neo4j 6.2 driver and 2026.05 server"), which moved the HA deployment and Terraform helm_release pins to the same 2026.5.0 chart, so the Helm and Terraform deployment paths stay on one Neo4j version.

Key changes

• Deployments get Neo4j 2026.05.0 instead of 2025.10.1, in line with what Infrahub 1.11 is tested against.
• appVersion moves to 1.11.0 on both charts, so they deploy the Infrahub release that carries the matching Neo4j 6.2 driver.
• infrahub chart 4.32.3 → 4.33.0; infrahub-enterprise 4.18.3 → 4.19.0 with its infrahub dependency repinned to 4.33.0.
• Changelog fragments on both charts flag the store upgrade for operators running a persistent data volume.

Operator impact

Neo4j 2026.05 upgrades the store format on first startup, and that is not reversible. Operators should back up the database before upgrading the chart — both changelog fragments say so.

The chart default for neo4j.volumes.data is emptyDir, so only deployments that opted into a persistent volume are affected.

Test plan

• helm lint passes on charts/infrahub and charts/infrahub-enterprise.
• Rendered manifests were diffed old (2025.10.1-4) vs new (2026.5.0) across the default values and all five infrahub-enterprise sizing presets (small, medium, large, medium-data, large-data). The only differences are image: neo4j:2025.10.1 → neo4j:2026.05.0 and the subchart's own HELM_NEO4J_VERSION / HELM_CHART_VERSION env vars. Nothing else in the StatefulSet moves.
• neo4j:2026.05.0 and neo4j:2026.05.0-enterprise both exist upstream as multi-arch (amd64 + arm64) images.
• All three towncrier fragments were draft-built and render correctly at 4.33.0 / 4.19.0.
• Rebased onto stable at d9ff224. Re-verified after the rebase: both charts lint, all six render cases still produce neo4j:2026.05.0 with no resource limits, and stable's medium-preset heap change (24G → 16G, fix: medium sizing preset reserves 28 GB of 32 GB for Neo4j, leaving no headroom #87) is intact.
• CI to watch: helm-lint-infrahub, helm-lint-enterprise, e2e-infrahub, e2e-infrahub-enterprise.

Commits

Three commits, reviewable independently:

1. chore(infrahub): upgrade the neo4j subchart to 2026.5.0 — the version bump itself.

2. refactor(infrahub): drop the neo4j resources limits workaround — removes the now-redundant limits: {} in values.yaml. It existed only because the older subchart forced limits == requests whenever limits was nil, so an explicit empty map was the only way to render Neo4j uncapped (af1a7d9). The 2026.5.0 helper only auto-fills limits for the shorthand resources.cpu/resources.memory form, so a requests-only block leaves them unset on its own.

   Equivalent rendered output — limits drops out entirely instead of rendering as {}, which is the same "no cap" to Kubernetes. Verified across the default values and all five sizing presets, plus both user-override paths: a shorthand cpu/memory override still does not auto-fill limits, and an explicit limits override still passes through untouched.

3. chore: bump appVersion to 1.11.0 — points both charts at the newly released Infrahub 1.11.0, following the existing bump convention: appVersion on both charts plus prefect-server.global.prefect.image.prefectTag in the infrahub values, which tracks the same version. Rendered manifests now pull registry.opsmill.io/opsmill/infrahub:1.11.0 (confirmed present in the registry) alongside neo4j:2026.05.0.

🤖 Generated with Claude Code