build(deps): update infrahub-sdk[all] requirement from <2.0.0,>=1.21.1 to >=1.22.1,<2.0.0

[dependabot]

Updates the requirements on infrahub-sdk[all] to permit the latest version.

Release notes

Sourced from infrahub-sdk[all]'s releases.

v1.22.1

1.22.1 - 2026-07-03

Added

• Added a shortest_paths_only parameter to InfrahubClient.traverse_paths() and its sync equivalent (default None, deferring to the server). Set it to False to return all loopless paths up to max_paths instead of only the shortest one(s); previously path traversal always returned the shortest path(s) because the flag could not be set. PathTraversalResult now also parses truncated_at_depth, which is set when the search stopped at max_depth before exhausting the graph and None when it completed within budget. (#1119)

Fixed

• Clarified the ValidationError raised when calling save(allow_upsert=True) on a node whose human-friendly identifier includes a CoreNumberPool-sourced attribute. The message now explains that the pool assigns a new value on every creation, so the HFID is never stable and the upsert would silently create a duplicate on each run, and points to the idempotent alternatives (look the node up by a stable field and reuse it, or set an explicit id). The resource manager guide was updated to match.

Changelog

Sourced from infrahub-sdk[all]'s changelog.

1.22.1 - 2026-07-03

Added

• Added a shortest_paths_only parameter to InfrahubClient.traverse_paths() and its sync equivalent (default None, deferring to the server). Set it to False to return all loopless paths up to max_paths instead of only the shortest one(s); previously path traversal always returned the shortest path(s) because the flag could not be set. PathTraversalResult now also parses truncated_at_depth, which is set when the search stopped at max_depth before exhausting the graph and None when it completed within budget. (#1119)

Fixed

• Clarified the ValidationError raised when calling save(allow_upsert=True) on a node whose human-friendly identifier includes a CoreNumberPool-sourced attribute. The message now explains that the pool assigns a new value on every creation, so the HFID is never stable and the upsert would silently create a duplicate on each run, and points to the idempotent alternatives (look the node up by a stable field and reuse it, or set an explicit id). The resource manager guide was updated to match.

1.22.0 - 2026-06-23

Added

• Added query_name parameter to all(), filters(), count() and get() methods in InfrahubClient and InfrahubClientSync to be used as meaningful GraphQL operation name for observability (#923)
• Add infrahubctl graphql query-report to analyze a GraphQL query and report whether it targets unique nodes, which controls whether Infrahub limits artifact regeneration to changed nodes or regenerates all artifacts on any relevant node change. Supports --online to fetch the query from the server by name.
• Added OrderByEntry and an Order.by field so query results can be ordered by attributes, related-node attributes, or node metadata, e.g. Order(by=[OrderByEntry(field="name__value", direction=OrderDirection.DESC)]). The Order.node_metadata field is deprecated; use by with the node_metadata__created_at / node_metadata__updated_at fields instead.
• Added graph traversal support for Infrahub 1.10: InfrahubClient.traverse_paths() (shortest path(s) between two nodes), InfrahubClient.reachable_nodes() (nodes of given kinds reachable from a source), and InfrahubClient.path_exists() (boolean convenience for checks) — all with sync equivalents. Source and destination accept either a node id or an InfrahubNode; kind filters accept kind strings or protocol classes; each PathNode in the result exposes .fetch() to resolve the full node (store-backed). Calling these against a pre-1.10 server raises a clear VersionNotSupportedError.

Fixed

• Calling .save(allow_upsert=True) on a node whose human-friendly identifier contains a CoreNumberPool-sourced attribute now raises a clear ValidationError instead of crashing with an opaque backend error. (#339)

• RelatedNode, RelatedNodeSync, RelationshipManager and RelationshipManagerSync are now generic over their peer type, and infrahubctl protocols parameterises generated relationships accordingly (e.g. device: RelatedNode[NetworkDevice], interfaces: RelationshipManager[NetworkInterface]).

  Traversing a relationship via .peer, .peers or indexing now preserves the peer's type instead of collapsing to the dynamic InfrahubNode, so chains such as device.rack.peer.name.value type-check under mypy/ty without casts. Existing un-parameterised RelatedNode / RelationshipManager usage is unaffected — the peer type defaults to InfrahubNode / InfrahubNodeSync, preserving current behaviour. (#1063) (#1063)

• Cardinality-one relationships in generated protocols are now typed with a RelationshipAttribute[...] descriptor. It still reads back as a typed RelatedNode[Peer] (so .peer keeps the peer type), but it accepts assignment of an id string, an HFID, a peer node, or None — mirroring the runtime InfrahubNode.__setattr__, which wraps the assigned value in a RelatedNode.

  Previously relationships were typed read-only as RelatedNode, so the documented way of setting a relationship (node.rel = "<id>" or node.rel = peer_node) failed under mypy/ty with an assignment error. The descriptor only appears in generated protocols and is never instantiated at runtime.

  Because the new typing lives in the generated protocols, existing projects must regenerate them with infrahubctl protocols to pick up the change — it does not take effect for already-generated protocol files. (#1064) (#1064)

• Calling .save(allow_upsert=True) on a node hydrated by from_graphql no longer silently clears optional one-cardinality relationships that the GraphQL response didn't fetch. Explicitly assigning node.rel = None still clears the relationship. (#1080)

• Send the GraphQL operation name as operationName in the request payload so tracing and observability tools can identify each query.

1.21.1 - 2026-06-05

Changed

• infrahubctl marketplace get --collection now downloads each member schema individually into a <output_dir>/<collection name>/<schema name>.yml layout (for example schemas/base-schemas/dcim.yml), instead of dumping version-suffixed files flat into the output directory. Filenames no longer carry the version, matching single-schema downloads, so re-downloading a collection overwrites cleanly rather than accumulating stale versions. If two members share a schema name across namespaces, those members are written to <output_dir>/<collection name>/<namespace>/<schema name>.yml instead of overwriting each other. (#1057)

Fixed

• Fix infrahubctl printing a spurious Error: 1 and Python traceback after the human-readable error message when a command exits with typer.Exit. The CLI now exits cleanly with only the intended error output. (#1047)

1.21.0 - 2026-05-29

Added

• Add infrahubctl marketplace get for fetching schemas and collections from the Infrahub Marketplace. Auto-detects schemas vs collections by namespace/name, supports --version for pinning, --collection to force the collection path, --stdout to stream content for piping (status messages on stderr), and --marketplace-url / INFRAHUB_MARKETPLACE_URL to point at staging or local instances. (#952)

Changed

... (truncated)

Commits

• c478a75 Prepare for release 1.22.1 (#1131)
• fedde45 Merge pull request #1125 from opsmill/ic-changelog-1119-path-traversal-shorte...
• 574c875 Add changelog newsfragment for path traversal shortest_paths_only (#1119)
• 0828e6d support for truncated_at_depth and shortest_paths_only (#1119)
• 1694cd0 Merge pull request #1113 from opsmill/dependabot/uv/stable/infrahub-testconta...
• 1e575a7 chore(deps-dev): bump infrahub-testcontainers from 1.9.8 to 1.10.0
• 4179e7a Merge pull request #1110 from opsmill/dga/chore-add-skills-a7fp7
• 578b54d Merge pull request #1109 from opsmill/dga/chore-upgrade-speckit-te5on
• 6a348cb chore: upgrade Spec Kit
• ef89f8d chore: add agentic skills for commit, PR, and issue workflows
• 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 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)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[cloudflare-workers-and-pages]

Deploying infrahub-demo-sp with    Cloudflare Pages

Latest commit:	a603e86
Status:	✅  Deploy successful!
Preview URL:	https://7820a26d.infrahub-demo-sp.pages.dev
Branch Preview URL:	https://dependabot-uv-main-infrahub-9u4o.infrahub-demo-sp.pages.dev

View logs