chore(deps-dev): bump infrahub-testcontainers from 1.11.8 to 1.11.9

Merged
DE
11d ago
+29-29

Bumps infrahub-testcontainers from 1.11.8 to 1.11.9.

Release notes

Sourced from infrahub-testcontainers's releases.

Infrahub - v1.11.9

Infrahub - v1.11.9 - 2026-10-22

Security

  • Updated certifi to 2026.10.19, which removes the emSign root certificates after intermediates were revoked due to key compromise (GHSA-6q48-6c7w-9gw2).

Changed

  • In the GraphQL schema, the node_metadata field of the NestedEdged type of every generic can now be null: its type changes from InfrahubNodeMetadata! to InfrahubNodeMetadata, as it already was on the NestedEdged types of node kinds. Teams that generate client types from the GraphQL schema will see node_metadata on these types as optional and must handle a null value. (#11100)
  • Artifacts and Generators that read a relationship with a filter are no longer regenerated when a change only affects related objects that the filter excludes.

Fixed

  • Fixed GraphQL queries failing with a "Cannot return null for non-nullable field" error when they requested node_metadata on a relationship whose peer kind is a generic. An empty cardinality-one relationship, such as the parent of a node at the top of a hierarchy, now returns node and node_metadata as null. The ancestors and descendants of a hierarchical node now return the node_metadata of each node. (#11100)
  • Fixed proposed changes that showed data conflicts on the fingerprint of Generator and Transformation definitions after another branch with Git changes was merged.
Changelog

Sourced from infrahub-testcontainers's changelog.

Infrahub - v1.11.9 - 2026-10-22

Security

  • Updated certifi to 2026.10.19, which removes the emSign root certificates after intermediates were revoked due to key compromise (GHSA-6q48-6c7w-9gw2).

Changed

  • In the GraphQL schema, the node_metadata field of the NestedEdged type of every generic can now be null: its type changes from InfrahubNodeMetadata! to InfrahubNodeMetadata, as it already was on the NestedEdged types of node kinds. Teams that generate client types from the GraphQL schema will see node_metadata on these types as optional and must handle a null value. (#11100)
  • Artifacts and Generators that read a relationship with a filter are no longer regenerated when a change only affects related objects that the filter excludes.

Fixed

  • Fixed GraphQL queries failing with a "Cannot return null for non-nullable field" error when they requested node_metadata on a relationship whose peer kind is a generic. An empty cardinality-one relationship, such as the parent of a node at the top of a hierarchy, now returns node and node_metadata as null. The ancestors and descendants of a hierarchical node now return the node_metadata of each node. (#11100)
  • Fixed proposed changes that showed data conflicts on the fingerprint of Generator and Transformation definitions after another branch with Git changes was merged.
Commits
  • a9fe185 chore: release 1.11.9
  • 986d1d8 chore: update docker-compose for release 1.11.9
  • 50c84e0 feat(regeneration): leave out changes to peers a filtered relationship read e...
  • 9b155e3 chore(deps): bump pillow (#11181)
  • 7c80220 fix(deps): bump certifi to 2026.10.19 for GHSA-6q48-6c7w-9gw2 (#11170)
  • 43b382c test(graphql): regroup the relationship node_metadata tests (#11168)
  • 579d123 docs(testing): place component tests by topic and share their data load (#11158)
  • d52d21d docs: document task manager credentials in the least-privilege guide
  • 71a1faa Merge pull request #11118 from opsmill/feat/bug-11100-node-metadata-empty-par...
  • 9cfacf4 Merge pull request #11133 from opsmill/ds-pre-commit-skip-generated-whitespace
  • 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)