Skip to content

chore(deps-dev): bump infrahub-testcontainers from 1.10.2 to 1.10.3#1176

Open
dependabot[bot] wants to merge 1 commit into
stablefrom
dependabot/uv/stable/infrahub-testcontainers-1.10.3
Open

chore(deps-dev): bump infrahub-testcontainers from 1.10.2 to 1.10.3#1176
dependabot[bot] wants to merge 1 commit into
stablefrom
dependabot/uv/stable/infrahub-testcontainers-1.10.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 13, 2026

Copy link
Copy Markdown
Contributor

Bumps infrahub-testcontainers from 1.10.2 to 1.10.3.

Release notes

Sourced from infrahub-testcontainers's releases.

Infrahub - v1.10.3

Added

  • Global initialization locks now expire automatically after a configurable time-to-live (20 minutes by default, set via INFRAHUB_CACHE_INIT_LOCK_TTL_MINS). Previously, if a worker died while holding the task-manager or registry initialization lock, the lock was never released and Infrahub could not start until the key was manually deleted from Redis. The lock now auto-expires so the platform recovers on its own. This applies to the Redis cache driver. (#9277)

Fixed

  • The search bar now finds an IPv6 address or prefix entered with a prefix length regardless of how it is written. Previously, typing an IPv6 value with host bits set (for example 2a0b:2081:1:d3::1/127), or its non-collapsed extended form, returned no matching object even when one existed, because the value was not normalized before the lookup. (#9788)
  • Running Check connectivity on a repository now records the outcome in the repository's operational status. Previously a failed check (for example an unreachable Git server returning an HTTP 504) was only shown to the caller, so the repository kept displaying Online and In sync while it was actually unreachable. A failed check now sets the status to Connectivity Error, Credential Error, or Error, and a successful check sets it back to Online. HTTP 5xx gateway errors and connection timeouts are now classified as connection errors. (#9818)
  • Filtering tasks by an id that is not a valid UUID now returns a validation error instead of an internal server error.
  • Fix diff calculation to correctly handle the case when a relationship was removed from a branch's schema while the other branch changed a non-peer property (source, owner, or protected flag) of that relationship. This issue would have previously appeared as a DiffNoPeerIdError.
  • Fixed exhaustive path traversal (shortest_paths_only: false) so it no longer tries to search through graphs that are too dense. When the paths through a node fan out too far to enumerate within budget, the search now stops and reports how deep it got via truncated_at_depth, instead of building an unbounded set of paths in memory. It also no longer returns spurious or duplicate paths through a node that has been renamed or re-parented by a schema migration.
  • Fixed the branch merge rollback so that a database error (such as an out-of-memory error) raised partway through the bulk merge queries no longer leaves partially merged data on the destination branch. The rollback now removes every change stamped with the merge timestamp even when the failure occurred before the merge finished discovering the affected nodes.
  • The task GraphQL query now returns the correct log count when only logs { count } is selected, without requesting the log entries themselves.

Full Changelog: opsmill/infrahub@infrahub-v1.10.2...infrahub-v1.10.3

Changelog

Sourced from infrahub-testcontainers's changelog.

Infrahub - v1.10.3 - 2026-07-07

Added

  • Global initialization locks now expire automatically after a configurable time-to-live (20 minutes by default, set via INFRAHUB_CACHE_INIT_LOCK_TTL_MINS). Previously, if a worker died while holding the task-manager or registry initialization lock, the lock was never released and Infrahub could not start until the key was manually deleted from Redis. The lock now auto-expires so the platform recovers on its own. This applies to the Redis cache driver. (#9277)

Fixed

  • The search bar now finds an IPv6 address or prefix entered with a prefix length regardless of how it is written. Previously, typing an IPv6 value with host bits set (for example 2a0b:2081:1:d3::1/127), or its non-collapsed extended form, returned no matching object even when one existed, because the value was not normalized before the lookup. (#9788)
  • Running Check connectivity on a repository now records the outcome in the repository's operational status. Previously a failed check (for example an unreachable Git server returning an HTTP 504) was only shown to the caller, so the repository kept displaying Online and In sync while it was actually unreachable. A failed check now sets the status to Connectivity Error, Credential Error, or Error, and a successful check sets it back to Online. HTTP 5xx gateway errors and connection timeouts are now classified as connection errors. (#9818)
  • Filtering tasks by an id that is not a valid UUID now returns a validation error instead of an internal server error.
  • Fix diff calculation to correctly handle the case when a relationship was removed from a branch's schema while the other branch changed a non-peer property (source, owner, or protected flag) of that relationship. This issue would have previously appeared as a DiffNoPeerIdError.
  • Fixed exhaustive path traversal (shortest_paths_only: false) so it no longer tries to search through graphs that are too dense. When the paths through a node fan out too far to enumerate within budget, the search now stops and reports how deep it got via truncated_at_depth, instead of building an unbounded set of paths in memory. It also no longer returns spurious or duplicate paths through a node that has been renamed or re-parented by a schema migration.
  • Fixed the branch merge rollback so that a database error (such as an out-of-memory error) raised partway through the bulk merge queries no longer leaves partially merged data on the destination branch. The rollback now removes every change stamped with the merge timestamp even when the failure occurred before the merge finished discovering the affected nodes.
  • The task GraphQL query now returns the correct log count when only logs { count } is selected, without requesting the log entries themselves.
Commits
  • 4948c58 chore: update docker-compose
  • 9d7b5ee prep release 1.10.3 (#9838)
  • e86d298 Merge pull request #9839 from opsmill/ajtm-1.9.10-to-stable
  • d9d8f4c Merge branch 'release-1.9.9' into ajtm-1.9.10-to-stable
  • f8ee86c prep release 1.9.10 (#9837)
  • 76eb5fc fix(backend): roll back partially merged data when a merge query fails (1.9 b...
  • 3dfc47d fix(backend): roll back partially merged data when a bulk merge query fails (...
  • 8c7da59 fix(git): reflect connection failures in repository operational status (#9820)
  • ca8b5a1 feat(lock): add TTL to global initialization locks
  • d990b76 fix(task): resolve Cubic findings in flow-run queries and retention (backport...
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by cubic

Updates dev dependency infrahub-testcontainers from 1.10.2 to 1.10.3 to use Infrahub v1.10.3 in integration tests. This includes auto-expiring init locks and stability fixes to reduce startup flakes.

Written for commit ad0545e. Summary will update on new commits.

Review in cubic

Bumps [infrahub-testcontainers](https://github.com/opsmill/infrahub) from 1.10.2 to 1.10.3.
- [Release notes](https://github.com/opsmill/infrahub/releases)
- [Changelog](https://github.com/opsmill/infrahub/blob/stable/CHANGELOG.md)
- [Commits](opsmill/infrahub@infrahub-v1.10.2...infrahub-v1.10.3)

---
updated-dependencies:
- dependency-name: infrahub-testcontainers
  dependency-version: 1.10.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the type/housekeeping Maintenance task label Jul 13, 2026
@dependabot dependabot Bot requested a review from a team as a code owner July 13, 2026 09:15
@dependabot dependabot Bot added the type/housekeeping Maintenance task label Jul 13, 2026
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 13, 2026

Copy link
Copy Markdown

Deploying infrahub-sdk-python with  Cloudflare Pages  Cloudflare Pages

Latest commit: ad0545e
Status: ✅  Deploy successful!
Preview URL: https://549ffcf4.infrahub-sdk-python.pages.dev
Branch Preview URL: https://dependabot-uv-stable-infrahu-csvk.infrahub-sdk-python.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type/housekeeping Maintenance task

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant