ci: update maintenance-operator version to ea1cbd9 (of branch network-operator-26.1.x)#2754
ci: update maintenance-operator version to ea1cbd9 (of branch network-operator-26.1.x)#2754nvidia-ci-cd wants to merge 1 commit into
Conversation
Signed-off-by: nvidia-ci-cd <svc-cloud-orch-gh@nvidia.com>
Greptile SummaryThis is an automated CI bump of the
Confidence Score: 4/5A 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
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
%%{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
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 |
There was a problem hiding this comment.
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!
Automated CI update for component 'maintenance-operator', created by GitHub actions reusable workflow run 28871740949 for release branch network-operator-26.1.x.