fix(deps): update patch digest dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Confidence
github.com/insomniacslk/dhcp	require	digest	ddd8a41 -> d3abe7c
github.com/k8snetworkplumbingwg/network-attachment-definition-client	require	patch	v1.7.0 -> v1.7.7
github.com/openshift/api	replace	digest	2987a59 -> e515d9c
github.com/openshift/client-go	replace	digest	05eb988 -> 6193816
github.com/rancher/rancher/pkg/apis	replace	digest	2207cfe -> 58abf49
k8s.io/gengo/v2	replace	patch	v2.0.0-20240228010128-51d4e06bde70 -> v2.0.0-20250903151518-081d64401ab4
k8s.io/kube-openapi	replace	digest	70dd376 -> 589584f

---

Release Notes

k8snetworkplumbingwg/network-attachment-definition-client (github.com/k8snetworkplumbingwg/network-attachment-definition-client)

v1.7.7: 1.7.7

Compare Source

This release contains a few fixes described below

Fix IP assignment for plugins without interface index
Restores behavior assigning IPs without interface index to the last network status, fixing a regression.

Minor update to net-attach-def_test.go in the pkg/utils package.

Allow multiple IP sources in NetworkSelectionElement
Removes restriction so both ipam-claim-reference and IPRequest can be used together for flexible IP management.

Full Changelog: k8snetworkplumbingwg/network-attachment-definition-client@v1.7.6...v1.7.7

v1.7.6

Compare Source

This release fixes a regression affecting CNI plugins that do not specify interfaces in their CNI ADD result.

Previously, IP addresses returned without an associated interface index were not being assigned to any network-status entry. This release restores the prior behavior by assigning such IPs to the last network status (i.e., the last sandboxed interface), ensuring consistent handling across plugins, especially those that omit the interfaces field entirely.

This change is important for compatibility with certain CNI plugins and maintains expected behavior from earlier versions of the net-attach-def library.

Special thanks to @​Brian-McM for identifying the issue and providing the fix!

v1.7.5

Compare Source

This release contains a fix related to the determination of the default interface, e.g. setting the default parameter to true in the network-status annotation based on the presence of a gateway in the CNI ADD success result ips.gateway and makes the determination of the default based on the first interface that has an associated value of gateway (using the interface index in the ips element in the CNI ADD success result).

This provides flexibility especially in CRI-O which uses the first interface and IP addresses for the pod.IP in Kubernetes, therefore. Containerd functionality is unchanged in that it uses the value for the IP addresses specifically

It's worth noting that CNI ADD success results which do not contain any interfaces will be discarded in this determination of the default, therefore it's recommended to set one with an associated gateway if aiming to have it be noted as the default.

v1.7.4

Compare Source

This release accounts for CNI plugins which do not use the sandbox field in results when calculating the network-status annotation, doing so for backwards compatibility for plugins which choose to not use this field (such as Calico)

v1.7.3

Compare Source

This release accounts for the sandox interfaces when reporting the interfaces in the network-status annotation; in case the CreateNetworkStatuses clients invoke it with a CNI result featuring non-sandbox interfaces as the first item in the list, this release accounts for that condition.

v1.7.2

Compare Source

When the CreateNetworkStatuses method was created to properly set the network-status annotation when a CNI result includes multiple interfaces in the return, it was found that it when setting the "default" parameter in the network-status, it was setting it to all the returned interfaces to true, which doesn't fit the NPWG net-attach-def specification.

This release fixes that issue by using the first interface in the CNI result set to "default": true for the cluster default network and not the following interfaces.

NOTE Do not use this version, use >= v1.7.3

v1.7.1

Compare Source

Adds the CreateNetworkStatuses method to properly set the network-status annotation when a CNI result includes multiple interfaces in the return.

For details of the before/after, see this gist: https://gist.github.com/dougbtv/1eb8ac2d61d494b56d65a6b236a86e61

For the related suggested update to the NPWG net-attach-def specification (for clarity only), see this proposal @​ https://docs.google.com/document/d/1DUTV-o6E6zlRTKZkxeDhAeyGrmq03qPgPbU580Rm7-g/edit

---

Configuration

📅 Schedule: Branch creation - "after 10am on sunday" in timezone Asia/Taipei, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 9 additional dependencies were updated

Details:

Package	Change
golang.org/x/sync	v0.12.0 -> v0.16.0
github.com/google/gnostic-models	v0.6.9 -> v0.7.0
golang.org/x/crypto	v0.36.0 -> v0.41.0
golang.org/x/mod	v0.23.0 -> v0.27.0
golang.org/x/net	v0.38.0 -> v0.43.0
golang.org/x/sys	v0.31.0 -> v0.35.0
golang.org/x/term	v0.30.0 -> v0.34.0
golang.org/x/text	v0.23.0 -> v0.28.0
golang.org/x/tools	v0.30.0 -> v0.36.0