Skip to content

ci: update maintenance-operator version to ea1cbd9 (of branch network-operator-26.1.x)#2754

Open
nvidia-ci-cd wants to merge 1 commit into
masterfrom
ci/update-maintenance-operator-version-to-ea1cbd9
Open

ci: update maintenance-operator version to ea1cbd9 (of branch network-operator-26.1.x)#2754
nvidia-ci-cd wants to merge 1 commit into
masterfrom
ci/update-maintenance-operator-version-to-ea1cbd9

Conversation

@nvidia-ci-cd

Copy link
Copy Markdown
Collaborator

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

Signed-off-by: nvidia-ci-cd <svc-cloud-orch-gh@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Jul 7, 2026

Copy link
Copy Markdown

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-apps Bot commented Jul 7, 2026

Copy link
Copy Markdown

Greptile Summary

This is an automated CI bump of the maintenance-operator component in both values.yaml and hack/release.yaml, replacing the previous tag network-operator-v26.7.0-beta.2 with the short commit SHA ea1cbd9 from branch network-operator-26.1.x.

  • The new version identifier is a 7-character short commit SHA rather than a full SHA or a semantic version tag, which reduces traceability and can become ambiguous over time.
  • The source branch (network-operator-26.1.x) predates the previous tag (v26.7.0-beta.2), meaning this update targets an earlier release line while the PR base is master — this version relationship is worth verifying is intentional.

Confidence Score: 4/5

A routine automated CI version bump across two files; the change is internally consistent but uses a short commit SHA instead of a full SHA or semantic tag, and the source branch is an older release line than the tag it replaces.

Both files are updated consistently and the change is confined to version strings. The main concern is the use of a 7-character short SHA as the image tag — short SHAs can collide in large repos and are harder to audit — and the apparent version step-back from the v26.7.0 series to a commit from network-operator-26.1.x while targeting master.

Both deployment/network-operator/values.yaml and hack/release.yaml carry the same short-SHA tag; confirming the 26.1.x commit is intentional for the master branch is the key check.

Important Files Changed

Filename Overview
deployment/network-operator/values.yaml Updates maintenance-operator image tag from semantic version network-operator-v26.7.0-beta.2 to short commit SHA ea1cbd9; consistent with release.yaml change
hack/release.yaml Updates maintenanceOperator version from network-operator-v26.7.0-beta.2 to short commit SHA ea1cbd9 from branch network-operator-26.1.x

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[CI Workflow\nmaintenance-operator\nbranch: network-operator-26.1.x] -->|triggers automated PR| B[PR #2754 targeting master]
    B --> C{Files Updated}
    C --> D[deployment/network-operator/values.yaml\ntag: network-operator-v26.7.0-beta.2\n→ ea1cbd9]
    C --> E[hack/release.yaml\nversion: network-operator-v26.7.0-beta.2\n→ ea1cbd9]
    D --> F[maintenance-operator image\nnvcr.io/nvstaging/mellanox/maintenance-operator:ea1cbd9]
    E --> F
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[CI Workflow\nmaintenance-operator\nbranch: network-operator-26.1.x] -->|triggers automated PR| B[PR #2754 targeting master]
    B --> C{Files Updated}
    C --> D[deployment/network-operator/values.yaml\ntag: network-operator-v26.7.0-beta.2\n→ ea1cbd9]
    C --> E[hack/release.yaml\nversion: network-operator-v26.7.0-beta.2\n→ ea1cbd9]
    D --> F[maintenance-operator image\nnvcr.io/nvstaging/mellanox/maintenance-operator:ea1cbd9]
    E --> F
Loading

Reviews (1): Last reviewed commit: "ci: update maintenance-operator version ..." | Re-trigger Greptile

repository: nvcr.io/nvstaging/mellanox
name: maintenance-operator
tag: network-operator-v26.7.0-beta.2
tag: ea1cbd9

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Short commit SHA used as image tag

The tag ea1cbd9 is a 7-character abbreviated commit SHA rather than a full SHA or a semantic version string. Short SHAs can become ambiguous as repository history grows and are harder to trace back to a specific release. Additionally, this change moves from the v26.7.0-beta.2 series to a commit on branch network-operator-26.1.x, which appears to be an earlier release line — worth confirming this version regression is intentional for the master base branch.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

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