Infrahub - v1.7.0rc0 (release candidate)

Infrahub v1.7.0rc0 - Release Notes

⚠ !!! WARNING This first release candidate of Infrahub v1.7.0 is supposed to be used for testing purposes only.

We're excited to announce the first release candidate of Infrahub, v1.7.0rc0! This release focuses on enhancing data governance and strengthening the platform foundation for enterprise deployments.

Version 1.7 introduces comprehensive audit capabilities with immutable metadata tracking, expands profile functionality to support relationships. Under the hood, we've upgraded critical backend dependencies to ensure optimal performance, security, and long-term maintainability.

Main changes

Object level meta data

Infrahub now automatically tracks who created and last modified every object in your infrastructure data. This foundational capability enables complete audit trails and accountability across your entire automation stack.

Every object now includes:

• Created by and updated by — user attribution for all changes
• Created at and updated at — precise timestamps for data lifecycle tracking

This metadata is available through the UI, GraphQL API and Python SDK, enabling you to determine who created or updated an object and at which time.

The metadata is read-only and survives across branch operations, ensuring you have a reliable audit trail even in complex version control workflows.

This positions Infrahub as enterprise-ready for organizations requiring detailed data provenance and accountability.

The created_at and updated_at metadata will be set for all objects, even those that were create before this feature.
The created_by and updated_by metadata will be set for objects that have been created or updated after this release, existing objects will not be backfilled.

Relationships in Profiles

Profiles now support relationships in addition to attributes, enabling you to define complete, reusable templates for entire classes of objects.

Previously, profiles could only set attribute values, limiting their usefulness and adoption. Now you can:

• Define relationships within a profile alongside attributes
• Create comprehensive templates that capture both data and connections
• Enforce data consistency across large inventories with less manual work
• Apply complete object configurations at scale

For example, you can now create a "Production Server Interface" profile that captures configurations, such as the speed and MTU and mode, but also automatically connect it to a specific VLAN.

This reduces manual configuration, minimizes errors when scaling automation projects, and ensures that relationships are consistently applied across your infrastructure data model.

Branch list page scaling

Several users of Infrahub, have a requirement to have a large number of branches active at any given time in Infrahub. The branch list page has been updated to provide a better user experience when you have a large number of branches.

The branch list page now uses the previously introduced InfrahubBranch GraphQL query, which provides pagination functionality for the branch query. In this release we have also introduced a partial_match filter, which allows a user to search for a branch by a partial name.

Additionally the branch list page displays the new object level metadata, which allows you to more easily find the branch that you are looking for.

Upgraded backend dependencies

The platform foundation has been strengthened with major version upgrades across all core backend components:

• Python: 3.12 → 3.13
• Neo4j: 2025.03 → 2025.10/11
• RabbitMQ: 3.13 → 4.2
• Redis: 7.2 → 8.x
• PostgreSQL: 14 → 18

These upgrades deliver:

• Enhanced performance across the platform
• Improved security with the latest patches
• Access to new features in underlying technologies
• Better long-term maintainability and support

The upgrades have been thoroughly tested to ensure compatibility and performance regression has been validated to maintain Infrahub's reliability standards.

Full changelog

Added

• Add search functionality to the branches list view, allowing users to filter branches by name. (#2107)

• Added ability to enable and disable webhooks (#6761)

• Add display label based GraphQL filters display_label__isnull, display_label__value and display_label__values

• Added metadata display in branch list view showing last rebase, last update, created at, and created by information

• Added partial_match parameter to InfrahubBranch query for case-insensitive substring filtering on branch names

• Display "No task" on branch details when task are empty.

• Improved menu in IPAM details view:

  • Replaced the three-dot menu with a clearly labeled Actions button to open menu
  • Added quick navigation to related tasks
  • Added convert object type action
  • Added icons for all menu items

Changed

• This refactors timestamp handling across query and relationship functions to accept only Timestamp types, updates all dependent code and tests accordingly, refreshes development environment files, and includes no user-facing changes. (#63)
• Improve branches list and details views to use the updated GraphQL API structure. (#2108)
• Changed DiffTreeSummary GraphQL type count fields to be non-optional (#7778)
• Upgraded backend dependencies: Neo4j to 2025.10.1, Redis to 8.4.0, RabbitMQ to 4.2.1, PostgreSQL to 18

Fixed

• Stop showing warnings for deprecated attribute schema fields (regex, min_length, max_length) when they are not used (#7995)
• Fixed issue with creating and deleting webhook automations for installations with a high number of automations in Prefect.
• Fixed relationship fields not being cleared when removing a profile from a node
• Fixed the display order of attributes and relationships in detail views.
• Re-enable running a single migration in infrahub db migrate using the --migration-number option
• Updating your account information now correctly refreshes the visible data, preventing outdated data from being shown.

infrahub - v1.7.0b0 (beta)

Infrahub v1.7.0b0 - Release Notes

⚠ !!! WARNING This first beta version of Infrahub v1.7.0 is supposed to be used for testing purposes only.

We're excited to announce the first beta release of Infrahub, v1.7.0b0! This release focuses on enhancing data governance and strengthening the platform foundation for enterprise deployments.

Version 1.7 introduces comprehensive audit capabilities with immutable metadata tracking, expands profile functionality to support relationships. Under the hood, we've upgraded critical backend dependencies to ensure optimal performance, security, and long-term maintainability.

Main changes

Object level meta data

Infrahub now automatically tracks who created and last modified every object in your infrastructure data. This foundational capability enables complete audit trails and accountability across your entire automation stack.

Every object now includes:

• Created by and updated by — user attribution for all changes
• Created at and updated at — precise timestamps for data lifecycle tracking

This metadata is available through the UI, GraphQL API and Python SDK, enabling you to determine who created or updated an object and at which time.

The metadata is read-only and survives across branch operations, ensuring you have a reliable audit trail even in complex version control workflows.

This positions Infrahub as enterprise-ready for organizations requiring detailed data provenance and accountability.

The created_at and updated_at metadata will be set for all objects, even those that were create before this feature.
The created_by and updated_by metadata will be set for objects that have been created or updated after this release, existing objects will not be backfilled.

At this stage it is not yet possible to order or filter objects in the GraphQL API using this metadata. We expect to deliver on this functionality in one of the next 1.7 beta releases.

Relationships in Profiles

Profiles now support relationships in addition to attributes, enabling you to define complete, reusable templates for entire classes of objects.

Previously, profiles could only set attribute values, limiting their usefulness and adoption. Now you can:

• Define relationships within a profile alongside attributes
• Create comprehensive templates that capture both data and connections
• Enforce data consistency across large inventories with less manual work
• Apply complete object configurations at scale

For example, you can now create a "Production Server Interface" profile that captures configurations, such as the speed and MTU and mode, but also automatically connect it to a specific VLAN.

This reduces manual configuration, minimizes errors when scaling automation projects, and ensures that relationships are consistently applied across your infrastructure data model.

Branch list page scaling

Several users of Infrahub, have a requirement to have a large number of branches active at any given time in Infrahub. The branch list page has been updated to provide a better user experience when you have a large number of branches.

The branch list page now uses the previously introduced InfrahubBranch GraphQL query, which provides pagination functionality for the branch query. In this release we have also introduced a partial_match filter, which allows a user to search for a branch by a partial name.

Additionally the branch list page displays the new object level metadata, which allows you to more easily find the branch that you are looking for.

Upgraded backend dependencies

The platform foundation has been strengthened with major version upgrades across all core backend components:

• Python: 3.12 → 3.13
• Neo4j: 2025.03 → 2025.10/11
• RabbitMQ: 3.13 → 4.2
• Redis: 7.2 → 8.x
• PostgreSQL: 14 → 18

These upgrades deliver:

• Enhanced performance across the platform
• Improved security with the latest patches
• Access to new features in underlying technologies
• Better long-term maintainability and support

The upgrades have been thoroughly tested to ensure compatibility and performance regression has been validated to maintain Infrahub's reliability standards.

Full changelog

Added

• Add search functionality to the branches list view, allowing users to filter branches by name. (#2107)

• Added partial_match parameter to InfrahubBranch query for case-insensitive substring filtering on branch names

• Display "No task" on branch details when task are empty.

• Improved menu in IPAM details view:

  • Replaced the three-dot menu with a clearly labeled Actions button to open menu
  • Added quick navigation to related tasks
  • Added convert object type action
  • Added icons for all menu items

Changed

• This refactors timestamp handling across query and relationship functions to accept only Timestamp types, updates all dependent code and tests accordingly, refreshes development environment files, and includes no user-facing changes. (#63)
• Improve branches list and details views to use the updated GraphQL API structure. (#2108)
• Upgraded backend dependencies: Neo4j to 2025.10.1, Redis to 8.4.0, RabbitMQ to 4.2.1, PostgreSQL to 18

Fixed

• Fixed relationship fields not being cleared when removing a profile from a node
• Fixed the display order of attributes and relationships in detail views.
• Updating your account information now correctly refreshes the visible data, preventing outdated data from being shown.

Infrahub - v1.6.2

Fixed

• Fix Migration041 to determine edge uniqueness correctly and account for incoming Relationship edges. Add new migration to un-delete improperly deleted Relationship metadata. This would only be a problem for Relationships between schemas that have both had their name, namespace, or kind updated multiple times. (#7916)

Full Changelog: infrahub-v1.6.1...infrahub-v1.6.2

Infrahub - v1.5.5

Fixed

• Fix Migration041 to determine edge uniqueness correctly and account for incoming Relationship edges. (#7916)

Full Changelog: infrahub-v1.5.4...infrahub-v1.5.5

Infrahub - v1.5.4

This release brings some bug-fixes to resolve issues found in Infrahub v1.5.3 and prior.

Fixed

• Fix an issue where removing a mandatory relationship was allowed. (#7853)

Full Changelog: infrahub-v1.5.3...infrahub-v1.5.4

Infrahub - v1.6.1

Infrahub - v1.6.1 - 2025-12-11

This release brings some bug-fixes to resolve issues found in Infrahub v1.6.0 and prior.

Added

• Add support for PKCE within Oauth2 and OIDC authentications. With this change the client_secret for Oauth2 and OIDC have been switched to being optional. PKCE is enabled by default but can be switched off in the configuration if required. (#7400)

Changed

• Upgrade infrahub-sdk to v1.17.0 (#7870)

Fixed

• Fix display_label not having a NULL value in the database when not set in the schema (#7704)
• Fixed schema cache issue when adding or removing dropdown/enum options via the UI, which causes intermittent "incorrect hash" errors after page refreshes. (#7780)
• Fix an issue where removing a mandatory relationship was allowed. (#7853)
• Fix breadcrumb display on CoreArtifactDefinition details page.
• Fixed form submission for schemas with only read-only attributes
• Improve branch creation and repository sync performance when having a lot of branches.

Infrahub - v1.6.0

We're excited to announce the release of Infrahub v1.6.0! This release brings significant improvements to Git integration, UI navigation, branch management, Profiles in Object Templates and introduces a new dashboard landing page.

Main changes

New dashboard landing page

We've replaced the static landing page with an interactive dashboard so you can immediately see what's happening in your Infrahub environment. The interactive dashboard shows:

1. Open proposed changes with status and review state
2. Git repositories sync status
3. Branches with quick details
4. Recent activity view the latest actions in Infrahub
5. Tasks overview the number of tasks that are running, completed, or that have failed.
6. Getting started with Infrahub – Access key resources like docs, labs, and tools.

Use Profiles in Object Templates

You can now define profiles in Object Templates so they're automatically applied when objects are created, ensuring consistency without manual post-creation steps.

Selective branch synchronization filter for Git repositories

Control which Git branches sync to Infrahub using configurable naming rules and patterns. Perfect for teams using multi-purpose repositories who want to keep Infrahub focused on relevant branches.

With this change you can now configure Infrahub to instead consult a list of branch names or regular expressions to determine if a given branch will be imported and created in Infrahub or not.

Explicit merge commits

Infrahub now optionally creates three-way merge commits instead of fast-forward merges, making it easy to trace Infrahub-originated merges in your Git repository history. You also have an option to configure the Git username and email that Infrahub will use to create the merge commit.

infrahubctl branch report command

The infrahubctl branch report command provides comprehensive status reports that help with branch cleanup and maintenance. When managing large environments with many branches, teams can now quickly identify which branches are safe to be removed.

The report displays:

• Branch metadata (creation time, sync status, schema changes)
• Git file changes detection
• Diff tree analysis with counts of added/updated/removed nodes
• Proposed changes summary with creator, approval status, and draft state

The infrahubctl branch report requires the installation of infrahub-sdk v1.16.0 with the ctl extra.

New breadcrumb navigation

Interactive breadcrumbs that adapt to your current view, show full object lineage, and let you switch between related objects directly.

Revamped hierarchy tree

We have redesigned the hierarchical tree to improve performance, and usability. This update addresses several long-standing issues and introduces a more intuitive navigation experience:

• Improved performance for large hierarchies
• Independent collapsing and navigation actions
• Resizable tree panel (10-50% of screen width)
• Smart loading when landing directly on detail views
• Better keyboard navigation and accessibility

Standardized label resolution in UI

All node labels will now resolve using this order:

1. If the schema defines a display_label, show node.display_label.
2. If not, but the schema defines an hfid, show node.hfid.
3. Otherwise, fall back to the node's id.

IPAM

The IPAM tree now uses the new hierarchy tree component (see changelog above) and is resizable.

Display Infrahub edition

See which Infrahub edition you're using in the account menu alongside the version.

Fixed nested convert_query_response

⚠ BREAKING CHANGE

When using convert_query_response with nested relationships in Python transforms and generators, queries must now include id and __typename fields on all nodes. This fixes a bug where objects were only converted one level deep.

If you are not using convert_query_response or if the queries that you are using with this feature aren't deeply nested, then you don't have to change anything.

Full changelog

Added

• Templates now support profile assignment. When both generate_template and generate_profile are configured on a schema node, profiles can be assigned to templates and will be automatically inherited by objects created from those templates. Profiles provide values for attributes not explicitly configured on the template, while template values take precedence when manually set. Multiple profiles can be assigned with proper priority handling. This enables bulk configuration updates across templated objects while maintaining consistency through profile inheritance. (#template-profiles)

• Merge core read only repositories on branch merge (#5978)

• IPAM tree is now resizable:

  • Adjust the width of the IPAM tree panel by dragging the divider
  • Tree panel can be resized between 10% and 50% of the screen width

  (#7262)

• You can now see which Infrahub edition you're using, displayed next to the app version in the account menu. (#7549)

• • Update the landing page documentation links to guide users in getting started with Infrahub.
  • Show Git repositories.
  • List branches on the landing page, sorted by creation date, with the main branch displayed first.
  • Include the proposed changes, showing only the key details.
  • Show recent activities, displaying only essential information.
  • Add tasks overview to display recent tasks and sort them by state.

• Add Explicit Merge Commits for Infrahub Branch Merges. These can be controlled via the INFRAHUB_GIT_USE_EXPLICIT_MERGE_COMMIT environment variable.
  The following environment variables are added:

  • INFRAHUB_GIT_USER_NAME
  • INFRAHUB_GIT_USER_EMAIL
  • INFRAHUB_GIT_GLOBAL_CONFIG_FILE
  • INFRAHUB_GIT_USE_EXPLICIT_MERGE_COMMIT

• Added branch filtering capability to selectively synchronize remote branches based on configurable import sync patterns.

• In the Proposed Changes data tabs, each node label is now a clickable link that takes you to the updated object’s detail page.

• New breadcrumb navigation:

  • Display full ancestors lineage of objects (parent objects or all ancestors for hierarchical schemas)
  • Display schema hierarchy for hierarchical schemas
  • Search and switch objects directly from breadcrumbs

• New hierarchy tree navigation:

  • It is now displayed in a dedicated and resizable sidebar on the left.
  • Added pagination on each level with infinite scroll.
  • Highlight current item in view.
  • Improved keyboard navigation and accessibility for easier browsing.
  • Clicking a chevron now expands or collapses the tree without opening the node detail.
  • Clicking a label now opens the node detail without expanding or collapsing the tree.

  When the user arrives directly on the detail view of a hierarchical object:

  • We will show a tree that only display the current node’s parent and siblings for faster loading.
  • Include a ‘Back’ button at the top, to return to the full tree view

Fixed

• Prevent long titles from overflowing event cards

  • Long titles now automatically truncate with ellipsis
  • Event cards no longer expand outside the visible area
  • Improves readability and keeps the UI layout intact

  (#activities-title)

• Display node labels using the following priority: display_label, then hfid, then id. (#display-labels)

• Backend database sessions are now handled consistently avoiding resource leakage.

• Fix retrieving human friendly ID and display label for relationship nodes via GraphQL, incorrect values could be returned instead of the ones stored in the database

• Fixed a UI issue that prevented the sidebar from fully collapsing when a link existed at the top level.

Infrahub - v1.6.0b0 (Beta)

⚠ !!! WARNING This first beta version of Infrahub v1.6.0 is supposed to be used for testing purposes only.

Main changes

New landing page

We've replaced the previous landing page with a new dashboard so you can immediately see what's happening in your Infrahub environment. The page is divided into several widgets:

1. Open proposed changes – See all open changes with their status and review state.
2. Git repositories – Check which repositories are connected and whether they are in sync.
3. Branches – Quickly review recent branches with basic details.
4. Recent activity – View the latest actions to understand who changed what and when.
5. Tasks overview – Monitor the number of tasks that are running, completed, or failed.
6. Getting started with Infrahub – Access key resources like docs, labs, and tools for new setups.

Add selective sync filter for Git repositories

Ability to control which branches are imported from a Git remote. By default Infrahub will constantly sync any managed repositories connected to Infrahub and create a new branch within Infrahub as soon as a new branch is pushed to the Git server.

With this change you can now configure Infrahub to instead consult a list of branch names or regular expressions to determine if a given branch will be imported and created in Infrahub or not.

[UI] New breadcrumb navigation

The breadcrumb is now interactive and adapts to the current Infrahub view and data model. It can:

• Show full object context and lineage (ancestors, parent objects, current object, schema, etc.).
• Let you switch between related objects directly from the breadcrumb.

[UI] hierarchy tree updated

We have revamped the hierarchical tree to improve stability, performance, and usability. This update addresses several long-standing issues and introduces a more intuitive navigation experience:

• Improved performance for large hierarchies
• Collapsing and navigating to a tree item will be independent actions.

On top of that, When you land directly on the detail view of a hierarchical object during the app's initial load:

• The tree shows only the object's parent and siblings for a faster first view.
• A Back button lets you return to the full tree at any time.

Provide option to add explicit merge commit during repository merge operations

When you merge a branch in Infrahub and the branch has a connected managed repository the branch within the repository will also be merged. Previously this was done with a fast forward merge. Infrahub 1.6 now has a configuration option to instead do a three way merge.

As commits from Infrahub now can show up in the Git logs, you also have the option of configuring the Git username and email that Infrahub will use.

Standardized label resolution in UI

All node label will resolve using this will resolve the label using this order:

1. If the schema defines a display_label, show node.display_label.
2. If not, but the schema defines an hfid, show node.hfid.
3. Otherwise, fall back to the node's id.

IPAM

• The IPAM tree now uses the new hierarchy tree component (see changelog above).
• The IPAM tree panel is now resizable.

Fixed nested convert_query_response

Breaking: When using Python transforms and generators in combination with the convert_query_response feature there was a previous problem where objects would only be converted one level deep when traversing relationships. This has now been corrected. In order for this to work all queries where the convert_query_response feature is enabled has to use query for id and __typename on all nodes that will show up within the response. Because of this change ensure that all queries targeting nodes include these fields, if you are not using the convert_query_response feature or if your queries using this feature isn't deeply nested you don't have to change anything.

Display Infrahub edition

You can now see which Infrahub edition you're using, shown next to the app version in the account menu.

Full changelog

Added

• Merge core read only repositories on branch merge (#5978)

• IPAM tree is now resizable:

  • Adjust the width of the IPAM tree panel by dragging the divider
  • Tree panel can be resized between 10% and 50% of the screen width
    (#7262)

• You can now see which Infrahub edition you're using, displayed next to the app version in the account menu. (#7549)

• Redesign landing page

  • Update the landing page documentation links to guide users in getting started with Infrahub.
  • Show Git repositories.
  • List branches on the landing page, sorted by creation date, with the main branch displayed first.
  • Include the proposed changes, showing only the key details.
  • Show recent activities, displaying only essential information.
  • Add tasks overview to display recent tasks and sort them by state.

• Add Explicit Merge Commits for Infrahub Branch Merges. These can be controlled via the INFRAHUB_GIT_USE_EXPLICIT_MERGE_COMMIT environment variable.
  The following environment variables are added:

  • INFRAHUB_GIT_USER_NAME
  • INFRAHUB_GIT_USER_EMAIL
  • INFRAHUB_GIT_GLOBAL_CONFIG_FILE
  • INFRAHUB_GIT_USE_EXPLICIT_MERGE_COMMIT

• Added branch filtering capability to selectively synchronize remote branches based on configurable import sync patterns.

• In the Proposed Changes data tabs, each node label is now a clickable link that takes you to the updated object’s detail page.

• New breadcrumb navigation:

  • Display full ancestors lineage of objects (parent objects or all ancestors for hierarchical schemas)
  • Display schema hierarchy for hierarchical schemas
  • Search and switch objects directly from breadcrumbs

• New hierarchy tree navigation:

  • It is now displayed in a dedicated and resizable sidebar on the left.
  • Added pagination on each level with infinite scroll.
  • Highlight current item in view.
  • Improved keyboard navigation and accessibility for easier browsing.
  • Clicking a chevron now expands or collapses the tree without opening the node detail.
  • Clicking a label now opens the node detail without expanding or collapsing the tree.
    When the user arrives directly on the detail view of a hierarchical object:
  • We will show a tree that only display the current node’s parent and siblings for faster loading.
  • Include a ‘Back’ button at the top, to return to the full tree view

Fixed

• Display node labels using the following priority: display_label, then hfid, then id. (#display-labels)
• Fixed bug that prevented retrieving cardinality-one relationships on a branch that was already merged and included changes to the relationship.
  This bug would be visible to the user as errors that look like ValidationError: Too many relationships, max 1 at field_name (#7338)
• Enable caching of the task count in order to avoid performance issues when having a long task history. (#7568)
• Refactor task setup to avoid excessive tasks being scheduled for branches that previously didn't contain tasks. The updated behaviour is that the task will only be triggered on the branch if the task signature differs from that of the default branch. (#7692)
• Delete branch-aware human friendly ID and display label attributes from branch-agnostic nodes if they were erroneously added. Add branch-agnostic human friendly ID and display label attributes to branch-agnostic nodes and set their values. (#7694)
• Backend database sessions are now handled consistently avoiding resource leakage.
• Fixed a UI issue that prevented the sidebar from fully collapsing when a link existed at the top level.

Infrahub - v1.5.3

This release brings some bug-fixes to resolve issues found in Infrahub v1.5.2 and prior.

Fixed

• Fixed bug that prevented retrieving cardinality-one relationships on a branch that was already merged and included changes to the relationship.
  This bug would be visible to the user as errors that look like ValidationError: Too many relationships, max 1 at field_name (#7338)
• Enable caching of the task count in order to avoid performance issues when having a long task history. (#7568)
• Refactor task setup to avoid excessive tasks being scheduled for branches that previously didn't contain tasks. The updated behaviour is that the task will only be triggered on the branch if the task signature differs from that of the default branch. (#7692)
• Delete branch-aware human friendly ID and display label attributes from branch-agnostic nodes if they were erroneously added. Add branch-agnostic human friendly ID and display label attributes to branch-agnostic nodes and set their values. (#7694)

Full Changelog: infrahub-v1.5.2...infrahub-v1.5.3

Infrahub - v1.5.2

This release brings some bug-fixes to resolve issues found in Infrahub v1.5.1 and prior.

Fixed

• Fix migration that backfills display labels and human-friendly IDs to account for schema that only exist on the branch being migrated.
  Add new migration to add display labels and human-friendly IDs to existing instances of templates and profiles. (#7655)
• Prevent attempting diff update on a deleted branch. Log a warning instead. (#7666)

Full Changelog: infrahub-v1.5.1...infrahub-v1.5.2