fix: update digest lookup to use versioned RepoTags instead of latest #3252
copy-pr-bot[bot]ci.yaml
on: push
variables
/
variables
7s
golang-checks
/
go-check
2m 17s
golang-checks
/
unit tests
37s
golang-checks
/
go-build
1m 54s
config-checks
/
helm-lint
8s
config-checks
/
validate-csv
47s
config-checks
/
validate-helm-values
35s
code-scanning
/
Analyze Go code with CodeQL
4m 15s
coverage
/
coverage
1m 14s
image-builds
/
build-gpu-operator-arm64
2m 27s
image-builds
/
build-gpu-operator-amd64
2m 36s
e2e-tests
/
e2e-tests-containerd
42m 8s
e2e-tests
/
e2e-tests-nvidiadriver
30m 51s
release
/
push-gpu-operator-bundle-image
Annotations
3 errors, 5 warnings, and 9 notices
|
e2e-tests / e2e-tests-containerd
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1935 exists
|
|
CI
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1935 exists
|
|
CI
Canceling since a higher priority waiting request for CI-refs/heads/pull-request/1935 exists
|
|
golang-checks / unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
golang-checks / go-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
coverage / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
image-builds / build-gpu-operator-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
image-builds / build-gpu-operator-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
variables / variables
Operator image: ghcr.io/nvidia/gpu-operator:fc3c9b6e
|
|
variables / variables
Push on build: true
|
|
variables / variables
Commit SHA: fc3c9b6e
|
|
image-builds / variables
Multi-arch image: ghcr.io/nvidia/gpu-operator:fc3c9b6e
|
|
image-builds / variables
Push on build: true
|
|
image-builds / variables
Commit SHA: fc3c9b6e
|
|
e2e-tests / variables / variables
Operator image: ghcr.io/nvidia/gpu-operator:fc3c9b6e
|
|
e2e-tests / variables / variables
Push on build: true
|
|
e2e-tests / variables / variables
Commit SHA: fc3c9b6e
|