ci: update spectrum-x-operator version to 76c2ceb (of branch network-operator-26.1.x)

[nvidia-ci-cd]

Automated CI update for component 'spectrum-x-operator', created by GitHub actions reusable workflow run 28871941198 for release branch network-operator-26.1.x.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Summary

This automated CI PR updates the spectrumXOperator.version in hack/release.yaml from network-operator-v26.7.0-beta.2 to 76c2ceb, a raw 7-character git commit SHA sourced from the network-operator-26.1.x branch.

• The new version is a bare commit SHA rather than a named release tag, diverging from every other component entry in the file and making the reference harder to audit and potentially fragile if upstream history is rewritten.
• The two STIG/FIPS variants (spectrumXOperatorStigFipsRhel, spectrumXOperatorStigFipsUbuntu) share the same sourceRepository but remain pinned to network-operator-v26.7.0-beta.2-* tags, creating a version split within the same component family.
• The PR description names the source as branch network-operator-26.1.x, while the target master tree tracks a v26.7.0-beta.2 release cycle — warranting confirmation that this cross-branch pin is intentional.

Confidence Score: 3/5

The change swaps a named release tag for a raw commit SHA sourced from a different release branch, leaving the STIG/FIPS variants of the same component at the prior tag — requires explicit confirmation before merging.

The updated version (76c2ceb) is a bare 7-char commit SHA from the network-operator-26.1.x branch, while every other entry in the file and the two companion STIG/FIPS variants of spectrum-x-operator remain at network-operator-v26.7.0-beta.2-style tags. This cross-release-branch pin could introduce an incompatible component into the 26.7.0 release tree, and the short SHA is harder to audit than a named tag.

hack/release.yaml — specifically the spectrumXOperator, spectrumXOperatorStigFipsRhel, and spectrumXOperatorStigFipsUbuntu sections, which now reference different release lines for the same upstream component.

Important Files Changed

Filename	Overview
hack/release.yaml	Updates spectrumXOperator.version from named tag network-operator-v26.7.0-beta.2 to a raw 7-char commit SHA 76c2ceb; STIG/FIPS variant entries are left unchanged at their prior named versions, creating an inconsistency within the same source repo.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[hack/release.yaml] --> B[spectrumXOperator]
    A --> C[spectrumXOperatorStigFipsRhel]
    A --> D[spectrumXOperatorStigFipsUbuntu]

    B --> B1["version: 76c2ceb (commit SHA)\n⚠ from branch network-operator-26.1.x"]
    C --> C1["version: network-operator-v26.7.0-beta.2-stig-fips-rhel\n(unchanged)"]
    D --> D1["version: network-operator-v26.7.0-beta.2-stig-fips-ubuntu\n(unchanged)"]

    B1 -. "version mismatch" .-> C1
    B1 -. "version mismatch" .-> D1

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[hack/release.yaml] --> B[spectrumXOperator]
    A --> C[spectrumXOperatorStigFipsRhel]
    A --> D[spectrumXOperatorStigFipsUbuntu]

    B --> B1["version: 76c2ceb (commit SHA)\n⚠ from branch network-operator-26.1.x"]
    C --> C1["version: network-operator-v26.7.0-beta.2-stig-fips-rhel\n(unchanged)"]
    D --> D1["version: network-operator-v26.7.0-beta.2-stig-fips-ubuntu\n(unchanged)"]

    B1 -. "version mismatch" .-> C1
    B1 -. "version mismatch" .-> D1

Loading

_{Reviews (1): Last reviewed commit: "ci: update spectrum-x-operator version t..." | Re-trigger Greptile}

[greptile-apps]

Cross-release-branch version pinned to a raw commit SHA

Every other component in this file uses a named release tag (e.g. network-operator-v26.7.0-beta.2), but this PR replaces the spectrumXOperator version with a bare 7-character commit SHA (76c2ceb). The PR description explicitly states this SHA comes from the network-operator-26.1.x branch, while the rest of the file — including the two STIG/FIPS variants of spectrum-x-operator (spectrumXOperatorStigFipsRhel, spectrumXOperatorStigFipsUbuntu) — remains pinned to 26.7.0-beta.2-era tags. A component from a 26.1.x branch wired into a 26.7.0 release tree creates a potential API/schema mismatch, and a short SHA is not reproducibly resolvable if the upstream repo ever force-pushes or garbage-collects that commit. Was this intended to target a different base branch (e.g. a network-operator-26.1.x release branch in this repo)?