ci: update multus-cni version to 3711f09b (of branch network-operator-26.4.x)

[nvidia-ci-cd]

Automated CI update for component 'multus-cni', created by GitHub actions reusable workflow run 23172942718 for release branch network-operator-26.4.x.

[greptile-apps]

Greptile Summary

This is an automated CI PR that bumps the multus-cni version from the semantic tag network-operator-v26.1.0 to the abbreviated git commit SHA 3711f09b across all 5 relevant files (hack/release.yaml and four example NicClusterPolicy CRs), corresponding to the latest commit on the network-operator-26.4.x release branch.

• All five changed files receive the same single-line version update under the multus / Multus stanza, pointing to nvcr.io/nvstaging/mellanox/multus-cni:3711f09b.
• 3711f09b is an abbreviated (8-character) git commit SHA. Every other component in hack/release.yaml continues to use the network-operator-v26.1.0 semantic tag, making Multus the only component tracking a raw commit SHA at this time. This is expected for automated pre-release CI workflows where the upstream component hasn't been tagged yet.
• No application logic is changed; the only effect is which Docker image tag will be resolved for the Multus CNI component at deploy time.

Confidence Score: 4/5

• This PR is safe to merge; it is a straightforward automated version bump with no logic changes.
• All changes are mechanical single-line version updates in YAML config/example files. No code paths are altered. The version format (abbreviated SHA) is unconventional compared to the rest of the file but is expected for automated pre-release CI tracking, and no validation layer in the codebase restricts Multus version format. The only risk is deploying an untagged/pre-release Multus image in environments that pull from the staging registry.
• hack/release.yaml — the only semantic difference (abbreviated SHA vs. versioned tag) worth a manual sanity-check that the image nvcr.io/nvstaging/mellanox/multus-cni:3711f09b is available before merging.

Important Files Changed

Filename	Overview
hack/release.yaml	Updates Multus version from semantic tag network-operator-v26.1.0 to abbreviated git commit SHA 3711f09b, making it the only component using a non-semantic version string.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full.yaml	Example CR updated to reflect the new multus-cni version 3711f09b; no logic changes.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-ipoib.yaml	Example IPoIB CR updated to reflect the new multus-cni version 3711f09b; no logic changes.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-nvidia-ipam.yaml	Example NVIDIA IPAM CR updated to reflect the new multus-cni version 3711f09b; no logic changes.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr.yaml	Main example CR updated to reflect the new multus-cni version 3711f09b; no logic changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Automated CI Workflow\nnetwork-operator-26.4.x] -->|Detects new commit| B[multus-cni commit 3711f09b]
    B -->|Triggers PR| C[Update version in 5 files]
    C --> D[hack/release.yaml\nMultus.version]
    C --> E[example/crs/cr-full.yaml\nmultus.version]
    C --> F[example/crs/cr-ipoib.yaml\nmultus.version]
    C --> G[example/crs/cr-nvidia-ipam.yaml\nmultus.version]
    C --> H[example/crs/cr.yaml\nmultus.version]
    D -->|Read by release tooling| I[Image: nvcr.io/nvstaging/mellanox/multus-cni:3711f09b]
    E & F & G & H -->|Used as example| J[NicClusterPolicy CR\nsecondaryNetwork.multus]

Loading

_{Last reviewed commit: 4065ad4}