ci: update Spectrum-X Operator STIG components (Ubuntu: 87b43f6-ubuntu, RHEL: 87b43f6-rhel)

[nvidia-ci-cd]

Automated CI update for components 'spectrumXOperatorStigFipsUbuntu' and 'spectrumXOperatorStigFipsRhel', created by internal GitLab CI for release branch network-operator-26.1.x.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates the version strings for Spectrum-X Operator STIG FIPS components from semantic versioning format to short commit hash format.

Key Changes:

• spectrumXOperatorStigFipsRhel: network-operator-v26.1.0-beta.5-stig-fips-rhel → 87b43f6-rhel
• spectrumXOperatorStigFipsUbuntu: network-operator-v26.1.0-beta.5-stig-fips-ubuntu → 87b43f6-ubuntu

Critical Issues:

• The new version format is inconsistent with all other components in hack/release.yaml, which use semantic versioning (e.g., network-operator-v26.1.0-beta.5-stig-fips)
• The automated release workflow in .github/workflows/release.yaml (lines 172-179, 259-266) expects STIG FIPS component versions to follow the pattern ${COMPONENT_TAG}-stig-fips-${component_flavor} (e.g., network-operator-v26.1.0-beta.5-stig-fips-rhel)
• This version format change may cause the CI/CD pipeline to construct incorrect image tags when pulling from the container registry
• The wait-for-images job checks for image availability using the expected pattern, which will likely fail with these short hash versions

Confidence Score: 2/5

• This PR introduces a breaking versioning format change that is highly likely to disrupt automated release workflows
• The version format change from semantic versioning to short commit hashes is fundamentally incompatible with the existing CI/CD infrastructure. The release workflow hardcodes expectations for STIG FIPS component version patterns, and this deviation will likely cause image pull failures and pipeline breakage
• hack/release.yaml requires immediate attention - the version format must match the pattern expected by .github/workflows/release.yaml

Important Files Changed

Filename	Overview
hack/release.yaml	Changed spectrumXOperatorStigFips version format from semantic versioning (network-operator-v26.1.0-beta.5-stig-fips-{rhel

Sequence Diagram

sequenceDiagram
    participant CI as CI System (nvidia-ci-cd)
    participant PR as Pull Request
    participant ReleaseYAML as hack/release.yaml
    participant Workflow as .github/workflows/release.yaml
    participant Registry as nvcr.io/nvstaging/mellanox
    
    Note over CI,Registry: Automated Component Version Update
    CI->>ReleaseYAML: Update spectrumXOperatorStigFipsRhel version
    CI->>ReleaseYAML: network-operator-v26.1.0-beta.5-stig-fips-rhel → 87b43f6-rhel
    CI->>ReleaseYAML: Update spectrumXOperatorStigFipsUbuntu version
    CI->>ReleaseYAML: network-operator-v26.1.0-beta.5-stig-fips-ubuntu → 87b43f6-ubuntu
    CI->>PR: Create PR #2097 with changes
    
    Note over Workflow,Registry: Expected Release Process Flow
    Workflow->>ReleaseYAML: Read component definitions
    Workflow->>Workflow: Parse STIG FIPS components
    Workflow->>Workflow: Apply version pattern: ${COMPONENT_TAG}-stig-fips-${flavor}
    Note over Workflow: ⚠️ Expects format like:<br/>network-operator-v26.1.0-beta.5-stig-fips-rhel
    Workflow->>Registry: Pull image with constructed tag
    Registry-->>Workflow: ❌ May fail if 87b43f6-rhel doesn't match expected pattern

Loading

[greptile-apps]

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Version format 87b43f6-rhel is inconsistent with all other STIG FIPS components in this file, which use the pattern network-operator-v{VERSION}-stig-fips-{os} (e.g., line 36: network-operator-v26.1.0-beta.5-stig-fips). The release workflow at .github/workflows/release.yaml:172-179 expects STIG FIPS components to follow the ${COMPONENT_TAG}-stig-fips-${component_flavor} format. This short hash format may cause the automated release process to fail.

[greptile-apps]

Version format 87b43f6-ubuntu is inconsistent with all other STIG FIPS components in this file, which use the pattern network-operator-v{VERSION}-stig-fips-{os}. The release workflow at .github/workflows/release.yaml:172-179 expects STIG FIPS components to follow the ${COMPONENT_TAG}-stig-fips-${component_flavor} format. This short hash format may cause the automated release process to fail.