Release 1.10.4

Release Number	1.10.4
Release Date	July 13th, 2026
Tag	infrahub-v1.10.4

Added

• INFRAHUB_DB_ADDRESS now accepts a comma-separated list of cluster members.

Fixed

• The INFRAHUB_DB_DATABASE name validation now matches Neo4j's naming rules: names may contain dashes, must be 3-63 characters long, and may no longer end with a dot. Database names that contain dashes or dots are now correctly quoted when the database is created, so they no longer fail with a Cypher syntax error.
• Changing a Git repository's location now re-points the server-side clone and fetches from the new remote, instead of staying stuck on the previous commit. (#9811)
• The configure-action-rules background flow no longer crashes when a trigger rule references a group or Generator that does not resolve on the branch being read (a required relationship left dangling by a deleted, orphaned, or branch-missing peer). The offending rule is now skipped with a warning that names it, and the remaining trigger rules are reconciled normally instead of the whole flow aborting. (#9829)
• Outbound webhook payloads now include the account_id of the account that triggered the event again, instead of always sending null. (#9881)
• Changing the identifier of a relationship in a schema is now rejected with a "not supported" validation error instead of being silently incorrectly applied.
• Deleting a node with cascade now checks mandatory relationships across the full set of cascaded objects. Previously a node pulled into the delete by a cascade could be removed even while a mandatory relationship from an object outside the delete set still referenced it, leaving a dangling mandatory relationship. Such deletes are now correctly blocked with a validation error.
• Fixed a bug where some human-friendly ID (HFID) values were stored with non-string elements (such as numbers) instead of all strings. Fresh upgrades now normalize all values, and instances that already upgraded are repaired automatically on their next upgrade.