chore(deps-dev): bump infrahub-testcontainers from 1.11.11 to 1.12.1
Bumps infrahub-testcontainers from 1.11.11 to 1.12.1.
Release notes
Sourced from infrahub-testcontainers's releases.
Infrahub - v1.12.1
Security
- Updated documentation dependencies to address
minimatch, RE2JS, and UUID security advisories, and updatedminimatchin the frontend plugin template.Changed
- Getting the next available prefix in a parent prefix that holds many subnets is now faster.
- Loading many objects together with their relationships is now faster.
Fixed
- Fixed the utilization of an IP prefix with
is_poolset to true depending on the fields of the GraphQL query: a query that did not requestis_poolleft the network and broadcast addresses out of the usable total and returned a utilization that was too high. (#11260)- Fixed the single sign-on buttons on the login page, which did not open the identity provider when clicked. (#11541)
Infrahub - v1.12.0
Infrahub 1.12 focuses on how Infrahub works with your Git repositories. Before you merge an Infrahub branch, you can check which commit it imported from each repository and whether the import succeeded. If Infrahub cannot push a merge back to Git, you can view the cause and retry. The release also changes how number pools allocate numbers, reduces the processing after large merges, adds tracing for slow automation, and introduces dark mode as an alpha.
This release contains breaking changes that need action before you upgrade. See Before you upgrade.
Release highlights
- Review changes to automation and data together with greater confidence. Verify that schemas, templates, Transformations, and Generator definitions have been imported successfully from Git before merging an Infrahub branch. If synchronization fails, you can identify the cause and recover while continuing to test changes on other branches.
- Automate on the infrastructure you already operate. Record the numbers your objects already hold in a number pool and allocate new numbers alongside them. A pool can now contain multiple ranges and keep a separate allocation sequence for each site or other scope.
- Keep making changes efficiently as your infrastructure grows. Reduce the processing required to update computed attributes and validate large Proposed Changes, and trace slow Generators, Transformations, and API requests to identify where time is spent.
- Work in dark mode (https://github.com/opsmill/infrahub/blob/HEAD/alpha). Choose a dark appearance or match your operating system's theme.
Before you upgrade
Review the breaking changes and required actions, particularly if you use any of the following:
If you use… Preparation Generators that manage objects Before upgrading, update each Generator to save every object it must retain on every run, including unchanged objects. Git repositories that define objects Before upgrading, restore any removed object files and their objects:entries if you want to retain those objects in Infrahub.SSO with existing accounts Link existing accounts to their SSO identities before the account-name fallback default changes. Experimental NATS drivers Before upgrading, replace the NATS message broker with RabbitMQ and the NATS cache with Redis. Number pools for unique attributes Before allocating numbers after upgrading, record existing assignments in their pools and resolve overlapping pool ranges. Local infrahubctlcommandsBefore running Generators, Transformations, or checks after upgrading, select the intended Infrahub branch explicitly or enable selection from your current Git branch. Announcing Dark Mode
You can now work in Infrahub in dark mode or match your operating system's appearance. The Theme menu in your account offers Dark, Light, and System. Dark mode is available as an alpha; some pages may still display incorrect colors.
Review and troubleshoot Git repository changes
Before merging an Infrahub branch, you can now confirm that it successfully imported the intended changes to schemas, templates, and automation definitions stored in a connected Git repository. If the merge completes in Infrahub but updating Git fails, you can also resolve that error without repeating the Infrahub merge.
... (truncated)
Changelog
Sourced from infrahub-testcontainers's changelog.
Infrahub - v1.12.1 - 2026-11-12
Security
- Updated documentation dependencies to address
minimatch, RE2JS, and UUID security advisories, and updatedminimatchin the frontend plugin template.Changed
- Getting the next available prefix in a parent prefix that holds many subnets is now faster.
- Loading many objects together with their relationships is now faster.
Fixed
- Fixed the utilization of an IP prefix with
is_poolset to true depending on the fields of the GraphQL query: a query that did not requestis_poolleft the network and broadcast addresses out of the usable total and returned a utilization that was too high. (#11260)- Fixed the single sign-on buttons on the login page, which did not open the identity provider when clicked. (#11541)
Infrahub - v1.12.0 - 2026-11-10
Infrahub 1.12 focuses on how Infrahub works with your Git repositories. Before you merge an Infrahub branch, you can check which commit it imported from each repository and whether the import succeeded. If Infrahub cannot push a merge back to Git, you can view the cause and retry. The release also changes how number pools allocate numbers, reduces the processing after large merges, adds tracing for slow automation, and introduces dark mode as an alpha.
This release contains breaking changes that need action before you upgrade. See Before you upgrade.
Release highlights
- Review changes to automation and data together with greater confidence. Verify that schemas, templates, Transformations, and Generator definitions have been imported successfully from Git before merging an Infrahub branch. If synchronization fails, you can identify the cause and recover while continuing to test changes on other branches.
- Automate on the infrastructure you already operate. Record the numbers your objects already hold in a number pool and allocate new numbers alongside them. A pool can now contain multiple ranges and keep a separate allocation sequence for each site or other scope.
- Keep making changes efficiently as your infrastructure grows. Reduce the processing required to update computed attributes and validate large Proposed Changes, and trace slow Generators, Transformations, and API requests to identify where time is spent.
- Work in dark mode (https://github.com/opsmill/infrahub/blob/stable/alpha). Choose a dark appearance or match your operating system's theme.
Before you upgrade
Review the breaking changes and required actions, particularly if you use any of the following:
If you use… Preparation Generators that manage objects Before upgrading, update each Generator to save every object it must retain on every run, including unchanged objects. Git repositories that define objects Before upgrading, restore any removed object files and their objects:entries if you want to retain those objects in Infrahub.SSO with existing accounts Link existing accounts to their SSO identities before the account-name fallback default changes. Experimental NATS drivers Before upgrading, replace the NATS message broker with RabbitMQ and the NATS cache with Redis. Number pools for unique attributes Before allocating numbers after upgrading, record existing assignments in their pools and resolve overlapping pool ranges. Local infrahubctlcommandsBefore running Generators, Transformations, or checks after upgrading, select the intended Infrahub branch explicitly or enable selection from your current Git branch. Announcing Dark Mode
You can now work in Infrahub in dark mode or match your operating system's appearance. The Theme menu in your account offers Dark, Light, and System. Dark mode is available as an alpha; some pages may still display incorrect colors.
Review and troubleshoot Git repository changes
Before merging an Infrahub branch, you can now confirm that it successfully imported the intended changes to schemas, templates, and automation definitions stored in a connected Git repository. If the merge completes in Infrahub but updating Git fails, you can also resolve that error without repeating the Infrahub merge.
... (truncated)
Commits
311b91fchore: release 1.12.1 (#11556)dca4380fix(frontend): open the identity provider from the SSO login buttons (#11542)aa53dcbfix(ipam): load is_pool at the time of the query9342088fix(ipam): load is_pool before computing the utilization of an IP prefixaff8c6bstyle(backend): re-enable ruff UP035 for backend/infrahub (#11550)266bd74docs: explain that webhooks are read from the default branch (#11184)a7858ddfix(deps): resolve remaining npm security update blockers (#11540)109db55perf(node): build the valid field names once per node (#11532)20a9500docs: fix four statements that contradict the code (#11537)e676882Refresh npm lockfiles to fix Dependabot alerts (#11533)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
