Prepare release/26.04 #1589
AyodeAwepublish.yml
on: push
docker
/
compute-matrix
5s
docker
/
checks
14s
Matrix: docker / build-rapids
Matrix: docker / build-cuvs
Matrix: docker / build-rapids-multiarch-manifest
Matrix: docker / test
Waiting for pending jobs
Matrix: docker / build-cuvs-multiarch-manifest
Matrix: docker / validate
Matrix: readme
Annotations
45 warnings
|
docker / checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (13.1.1) / build-cuvs (13.1.1, py3.12, arm64, ubuntu24.04, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (13.1.1) / build-cuvs (13.1.1, py3.11, arm64, ubuntu24.04, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (13.1.1) / build-cuvs (13.1.1, py3.13, arm64, ubuntu24.04, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (13.1.1) / build-cuvs (13.1.1, py3.12, amd64, ubuntu24.04, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (12.9.1) / build-cuvs (12.9.1, py3.12, arm64, ubuntu24.04, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (12.9.1) / build-cuvs (12.9.1, py3.13, arm64, ubuntu24.04, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (12.9.1) / build-cuvs (12.9.1, py3.11, arm64, ubuntu24.04, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (12.9.1) / build-cuvs (12.9.1, py3.12, amd64, ubuntu24.04, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (12.9.1) / build-cuvs (12.9.1, py3.11, amd64, ubuntu24.04, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (13.1.1) / build-cuvs (13.1.1, py3.11, amd64, ubuntu24.04, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (13.1.1) / build-cuvs (13.1.1, py3.13, amd64, ubuntu24.04, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (13.1.1) / build-rapids (13.1.1, py3.12, arm64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (13.1.1) / build-rapids (13.1.1, py3.13, arm64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (13.1.1) / build-rapids (13.1.1, py3.11, arm64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (13.1.1) / build-rapids (13.1.1, py3.12, amd64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs (12.9.1) / build-cuvs (12.9.1, py3.13, amd64, ubuntu24.04, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs-manifest (26.04a-cuda12.9.1-py3.13, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs-manifest (26.04a-cuda12.9.1-py3.11, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (13.1.1) / build-rapids (13.1.1, py3.13, amd64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs-manifest (26.04a-cuda13.1.1-py3.11, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs-manifest (26.04a-cuda13.1.1-py3.13, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs-manifest (26.04a-cuda12.9.1-py3.12, build_cpu=false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-cuvs-manifest (26.04a-cuda13.1.1-py3.12, build_cpu=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (13.1.1) / build-rapids (13.1.1, py3.11, amd64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (12.9.1) / build-rapids (12.9.1, py3.12, arm64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (12.9.1) / build-rapids (12.9.1, py3.12, amd64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (12.9.1) / build-rapids (12.9.1, py3.13, arm64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (12.9.1) / build-rapids (12.9.1, py3.11, amd64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (12.9.1) / build-rapids (12.9.1, py3.11, arm64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids (12.9.1) / build-rapids (12.9.1, py3.13, amd64, ubuntu24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids-manifest (26.04a-cuda12.9.1-py3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids-manifest (26.04a-cuda13.1.1-py3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids-manifest (26.04a-cuda12.9.1-py3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids-manifest (26.04a-cuda12.9.1-py3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids-manifest (26.04a-cuda13.1.1-py3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / build-rapids-manifest (26.04a-cuda13.1.1-py3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / validate (13) / validate (13, py3.13, amd64, h100, latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / validate (13) / validate (13, py3.13, amd64, h100, latest)
Restore cache failed: Dependencies file is not found in /home/runner/_work/docker/docker. Supported file pattern: go.mod
|
|
docker / validate (13) / validate (13, py3.13, arm64, l4, latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / validate (13) / validate (13, py3.13, arm64, l4, latest)
Restore cache failed: Dependencies file is not found in /home/runner/_work/docker/docker. Supported file pattern: go.mod
|
|
docker / validate (12) / validate (12, py3.12, amd64, l4, latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / validate (12) / validate (12, py3.12, amd64, l4, latest)
Restore cache failed: Dependencies file is not found in /home/runner/_work/docker/docker. Supported file pattern: go.mod
|
|
docker / validate (12) / validate (12, py3.11, arm64, a100, earliest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
docker / validate (12) / validate (12, py3.11, arm64, a100, earliest)
Restore cache failed: Dependencies file is not found in /home/runner/_work/docker/docker. Supported file pattern: go.mod
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
rapidsai~docker~2DTVE0.dockerbuild
|
94.9 KB |
sha256:e95d74e40f23a6997cbd2aa0f5cb9ef59cd2f61b2bf2979b46e8c0f11dac35b8
|
|
|
rapidsai~docker~2SI6BS.dockerbuild
|
78.4 KB |
sha256:089f1754c2a0745f0d60f368c1fe4609c1f5b193e47f1ebf7fc11d12b7f6a67d
|
|
|
rapidsai~docker~3GAD3Z.dockerbuild
|
118 KB |
sha256:28db0f8432bccc9a82379cdb35f5264a703072d32c525d9aee765673170eb57d
|
|
|
rapidsai~docker~3X9ZN3.dockerbuild
|
104 KB |
sha256:ef0f084fe4630cc96908669ce63274aea9da4791924ee9df3a489cd128e8e7f0
|
|
|
rapidsai~docker~4RNKOR.dockerbuild
|
80.6 KB |
sha256:9840844cb7323bef4a54a075e295e96127cf05ba48c1f57eb3b4d5b848bc426b
|
|
|
rapidsai~docker~4XPJHR.dockerbuild
|
80.2 KB |
sha256:3e6179c0f982f0a62a9817c606e5867f375c1c4e7b28d2c82fcbe42f3324cead
|
|
|
rapidsai~docker~4YDTTV.dockerbuild
|
101 KB |
sha256:f9009bc934f511aa2547336ccc84ce59063a95651509db3e6dba9923dd00be15
|
|
|
rapidsai~docker~8F3Q5U.dockerbuild
|
114 KB |
sha256:e5b072730d690ff47bde1739fffc42817403888131f2cccc743e4a0d8d01a704
|
|
|
rapidsai~docker~951OS1.dockerbuild
|
115 KB |
sha256:949e6997fdad837d57369d1cdf1fad22691c69ef6400f745d11af2fe99b7a35a
|
|
|
rapidsai~docker~CK8LPN.dockerbuild
|
119 KB |
sha256:540e43069fd27ea1627ac02550866391433457ce4d18f1d2e09a9ba12530f517
|
|
|
rapidsai~docker~DZ8PK5.dockerbuild
|
79.5 KB |
sha256:5b7a81d05d0deae957706f8ee704263bfa29d76c38290c895ece31aacfba5024
|
|
|
rapidsai~docker~GHLQH8.dockerbuild
|
55.2 KB |
sha256:bc708b1ec80ab752d6f08784f35ebf0d0e5593ede791472e60027056084833e9
|
|
|
rapidsai~docker~GO1BIM.dockerbuild
|
80.4 KB |
sha256:f79db973395e8780425776112526b86810a0952505ee92b609d749cab5357aa0
|
|
|
rapidsai~docker~GUGTAV.dockerbuild
|
80.8 KB |
sha256:5ed5dea6f1dfcb7bafff22a20471ac2e9c8e825e054ee5bf8ba78e283f3c1060
|
|
|
rapidsai~docker~H6J3RA.dockerbuild
|
120 KB |
sha256:331dd3299d9819225e8e97f56c9bf4ec56427b322302d5338c1dc83638d3cd07
|
|
|
rapidsai~docker~ICNJ7Y.dockerbuild
|
117 KB |
sha256:72546463826d0c2a520d4a77009c7327a7275b68bfe324e2775699bda0bcfa26
|
|
|
rapidsai~docker~JDZRTR.dockerbuild
|
113 KB |
sha256:2e5db716691bd6e897687ed78b366df807f21e1b845c9c953c86db44859ea58d
|
|
|
rapidsai~docker~M9CNPL.dockerbuild
|
102 KB |
sha256:a570c6093b1817a0e6d87172f971725f570faa859008a030fc57d5edc0b70393
|
|
|
rapidsai~docker~MBWP4K.dockerbuild
|
57.4 KB |
sha256:d01ce0b51ff57d277c434a7405c6673e2acc3ec5fc51c8c604b9444e428bc8af
|
|
|
rapidsai~docker~MC33QA.dockerbuild
|
79.5 KB |
sha256:9dc72e1ce926639e1f6423f396e76bbc5c2837d0e9a0267b1b0f6431b1d3f211
|
|
|
rapidsai~docker~MCDLDW.dockerbuild
|
110 KB |
sha256:3a2628ac6b10483e557b93c1285d1117a97a36fb9789478e8657ac1f704dd5a0
|
|
|
rapidsai~docker~MKQN12.dockerbuild
|
95.1 KB |
sha256:7604fd4735de90c898709d1def73ff67521bc782e1ba85422cc90f82804e8fbb
|
|
|
rapidsai~docker~MYNN2B.dockerbuild
|
80.4 KB |
sha256:9d126efd642470d2780208441f7e4ce227ad5431dd760548206e66a1378e952e
|
|
|
rapidsai~docker~PE6INM.dockerbuild
|
59.7 KB |
sha256:22d372dbf93e9e977d5836aa2d666e08bdf8665cb21c34f21429e803cde104bf
|
|
|
rapidsai~docker~PKZG01.dockerbuild
|
59.6 KB |
sha256:d77a96641d380db3af93a464033b0c42864f9f953b8f603f967cd2983fb79996
|
|
|
rapidsai~docker~Q2OIYC.dockerbuild
|
59.9 KB |
sha256:daf7c6b3c8bf127866b28b15d4aa3972ccc51910566207e0b61ffe3c424a0470
|
|
|
rapidsai~docker~Q5HYWH.dockerbuild
|
60.8 KB |
sha256:c3fc168c155fd8b25d37c32eb358eafe1f82fedcadf707e0285543461e7a89d4
|
|
|
rapidsai~docker~QBCAXO.dockerbuild
|
78.3 KB |
sha256:7e59db0881267178d31035705f78a454bf18424ef10926b3d962bef669f60cb1
|
|
|
rapidsai~docker~QGCN8Z.dockerbuild
|
79.6 KB |
sha256:3bc3f06899cd1bfcb8c66e48e240a830c8eec595551b1e9dba8cc5d98e479da9
|
|
|
rapidsai~docker~QGNJPR.dockerbuild
|
94.8 KB |
sha256:76ada85dc3d203701481c8ab4890640d4e997a57e208f98b881c4bc91c437547
|
|
|
rapidsai~docker~RHW3M7.dockerbuild
|
103 KB |
sha256:55ecee1988214cb0325f82c3736172b3d6998080fce5dc97e67296dd9d68de66
|
|
|
rapidsai~docker~RV0PEP.dockerbuild
|
89.8 KB |
sha256:20a5b18cc52470b4f6d6dfcb5ee96a26bad7e029af01697ae3aeb0c407ab31ad
|
|
|
rapidsai~docker~VFO52L.dockerbuild
|
79.4 KB |
sha256:0bcc49957928719a695f6d9c1b80ec6e599d08fd8e1342b390b370b361d414bc
|
|
|
rapidsai~docker~W7DZTY.dockerbuild
|
119 KB |
sha256:2cd2280cdb937142a4f6bfaee030d5bb6146cf74ee9471615c26e44d4bb1bcc5
|
|
|
rapidsai~docker~W7UEM4.dockerbuild
|
109 KB |
sha256:c3f8a1b652af704e466d10a84b98dcb600bc4ee5903de95d2712e0e3127b8017
|
|
|
rapidsai~docker~WNVQP5.dockerbuild
|
94.3 KB |
sha256:ccde1b2a125f06be23c1411045e0f48405ed37e04a89b8a7cb04d32daa745a8e
|
|
|
rapidsai~docker~X8JOE3.dockerbuild
|
80.4 KB |
sha256:8c2da7a08cccb632bfedd5595102de900a95a12a7b25308268be821a5facefb4
|
|
|
rapidsai~docker~XL1QY5.dockerbuild
|
86.8 KB |
sha256:202a8c87df3ddd17c371d7ccc8546f89ab782ad2056a3f14ba314fe990eb7a18
|
|
|
rapidsai~docker~YI7487.dockerbuild
|
103 KB |
sha256:94ce5e7477ca2719f3846ae91d12733ab879375dbba99e23c22567e6d64c9696
|
|
|
rapidsai~docker~YV8DBS.dockerbuild
|
94.9 KB |
sha256:b975be9f4d19e18dfec435de956a7314af7caa9564fa7e77a947d287efc679a4
|
|
|
rapidsai~docker~Z2BTQL.dockerbuild
|
112 KB |
sha256:ae9b5dc9e7600c22bc784d01fafc38a425bfcc019740399c4c5a7f98296a9583
|
|
|
rapidsai~docker~ZKIXQL.dockerbuild
|
93.8 KB |
sha256:d48b8ab9722c9553563b684fc6c9971cbc02c996cfb52be4ae1d2b72f5e78a5b
|
|