Skip to content

ci: update nic-configuration-operator version to 709c747 (of branch network-operator-26.1.x)#2178

Open
nvidia-ci-cd wants to merge 1 commit intomasterfrom
ci/update-nic-configuration-operator-version-to-709c747
Open

ci: update nic-configuration-operator version to 709c747 (of branch network-operator-26.1.x)#2178
nvidia-ci-cd wants to merge 1 commit intomasterfrom
ci/update-nic-configuration-operator-version-to-709c747

Conversation

@nvidia-ci-cd
Copy link
Collaborator

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

Signed-off-by: nvidia-ci-cd <svc-cloud-orch-gh@nvidia.com>
@greptile-apps
Copy link

greptile-apps bot commented Feb 13, 2026

Greptile Overview

Greptile Summary

Updated nic-configuration-operator and nic-configuration-operator-daemon versions from semantic version tag network-operator-v26.1.0-beta.7 to commit SHA 709c747 in release configuration and example custom resource files. This appears to be an automated CI update targeting a specific commit on the network-operator-26.1.x branch.

  • Version format changed from semantic tag to commit SHA for the base operator and daemon images
  • STIG FIPS variants still use the semantic version format (network-operator-v26.1.0-beta.7-stig-fips-*), which may need verification
  • Changes are consistent across all three modified files

Confidence Score: 3/5

  • This PR is moderately safe to merge with minor verification recommended
  • The changes are straightforward version updates for nic-configuration-operator components. However, the version format change from semantic versioning to commit SHA requires verification that the referenced commit exists and that STIG FIPS variants are intentionally left at the older semantic version.
  • Verify that STIG FIPS variant versions in hack/release.yaml are intentionally left unchanged

Important Files Changed

Filename Overview
hack/release.yaml Updated nicConfigurationOperator and nicConfigurationConfigDaemon versions from network-operator-v26.1.0-beta.7 to 709c747 (commit SHA). STIG FIPS variants still use the semantic version tag.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full.yaml Updated operator and configurationDaemon versions from network-operator-v26.1.0-beta.7 to 709c747 to match the release configuration.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full-ocp.yaml Updated operator and configurationDaemon versions from network-operator-v26.1.0-beta.7 to 709c747 to match the release configuration.

Last reviewed commit: ddd437e

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

repository: nvcr.io/nvstaging/mellanox
sourceRepository: nic-configuration-operator
version: network-operator-v26.1.0-beta.7
version: 709c747
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version format changed from semantic version tag (network-operator-v26.1.0-beta.7) to commit SHA (709c747). Verify that the STIG FIPS variants (lines 138, 144, 150, 156) shouldn't also be updated, as they still reference network-operator-v26.1.0-beta.7-stig-fips-*.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant