chore(infrahub): upgrade the neo4j subchart to 2026.5.0

charts/infrahub-enterprise/Chart.yaml

@@ -18,14 +18,14 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 4.18.3
+version: 4.19.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "1.10.9"
+appVersion: "1.11.0"
 
 dependencies:
   - name: infrahub
-    version: "4.32.3"
+    version: "4.33.0"
     repository: "oci://registry.opsmill.io/opsmill/chart"

charts/infrahub-enterprise/README.md

@@ -58,7 +58,7 @@ The chart offers the ability to configure persistence for the database and other
 
 | Repository | Name | Version |
 |------------|------|---------|
-| oci://registry.opsmill.io/opsmill/chart | infrahub | 4.32.0 |
+| oci://registry.opsmill.io/opsmill/chart | infrahub | 4.33.0 |
 
 ## Values
 

charts/infrahub-enterprise/changelog/+neo4j-2026.05.changed.md

@@ -0,0 +1 @@
+Bumped the `infrahub` dependency to 4.33.0, which upgrades the `neo4j` subchart from 2025.10.1-4 to 2026.5.0 (Neo4j 2026.05.0). Deployments using a persistent data volume will have their store upgraded by Neo4j on first startup, so back up the database before upgrading the chart.

charts/infrahub/Chart.yaml

@@ -18,16 +18,16 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 4.32.3
+version: 4.33.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "1.10.9"
+appVersion: "1.11.0"
 
 dependencies:
   - name: neo4j
-    version: "2025.10.1-4"
+    version: "2026.5.0"
     repository: "https://helm.neo4j.com/neo4j/"
     condition: neo4j.enabled
   - name: common

charts/infrahub/README.md

@@ -55,7 +55,7 @@ The chart offers the ability to configure persistence for the database and other
 
 | Repository | Name | Version |
 |------------|------|---------|
-| https://helm.neo4j.com/neo4j/ | neo4j | 2025.10.1-4 |
+| https://helm.neo4j.com/neo4j/ | neo4j | 2026.5.0 |
 | https://nats-io.github.io/k8s/helm/charts/ | nats | 1.1.12 |
 | https://prefecthq.github.io/prefect-helm | prefect-server | 2026.6.5172345 |
 | oci://registry-1.docker.io/bitnamicharts | common | 2.23.0 |
@@ -201,7 +201,6 @@ The chart offers the ability to configure persistence for the database and other
 | neo4j.neo4j.minimumClusterSize | int | `1` |  |
 | neo4j.neo4j.name | string | `"infrahub"` |  |
 | neo4j.neo4j.password | string | `"admin"` |  |
-| neo4j.neo4j.resources.limits | object | `{}` |  |
 | neo4j.neo4j.resources.requests.cpu | string | `"2"` |  |
 | neo4j.neo4j.resources.requests.memory | string | `"4Gi"` |  |
 | neo4j.services.admin.enabled | bool | `false` |  |

charts/infrahub/changelog/+appversion-1.11.0.changed.md

@@ -0,0 +1 @@
+Bumped `appVersion` to 1.11.0, so the chart deploys Infrahub 1.11 by default. 1.11 ships the Neo4j 6.2 Python driver, which is the driver Neo4j 2026.05 is validated against.

charts/infrahub/changelog/+neo4j-2026.05.changed.md

@@ -0,0 +1 @@
+Upgraded the `neo4j` subchart from 2025.10.1-4 to 2026.5.0, which deploys Neo4j 2026.05.0. This matches the Neo4j version Infrahub is tested against. Deployments using a persistent data volume will have their store upgraded by Neo4j on first startup, so back up the database before upgrading the chart.

charts/infrahub/changelog/+neo4j-resources-limits.housekeeping.md

@@ -0,0 +1 @@
+Dropped the explicit empty `neo4j.neo4j.resources.limits` map. The 2026.5.0 `neo4j` subchart only auto-fills limits for the shorthand `resources.cpu`/`resources.memory` form, so the requests-only block now leaves limits unset on its own. Neo4j still runs without a memory cap, and the rendered container is unchanged.

charts/infrahub/values.yaml

@@ -87,10 +87,10 @@ neo4j:
     minimumClusterSize: 1
     acceptLicenseAgreement: "no"
     resources:
-      # Neo4j's chart forces limits == requests when 'limits' is unset (nil).
-      # An explicit empty map is the only way to render the container with no
-      # resource limits, allowing Neo4j to burst above its requested memory.
-      limits: {}
+      # Deliberately no 'limits', so Neo4j can burst above its requested memory
+      # instead of being OOMKilled at an artificial cap. Neo4j's chart only
+      # auto-fills limits for the shorthand 'resources.cpu/memory' form, so a
+      # requests-only block leaves them unset.
       requests:
         cpu: "2"
         memory: "4Gi"
@@ -415,7 +415,7 @@ prefect-server:
     prefect:
       image:
         repository: registry.opsmill.io/opsmill/infrahub
-        prefectTag: 1.10.9
+        prefectTag: 1.11.0
   server:
     command:
       - /usr/bin/tini