Fix type annotation override #2604
mthrokpackaging.yml
on: pull_request
Matrix: Linux aarch64
Matrix: Linux x86_64 CUDA
Matrix: macOS
Matrix: Windows
Annotations
79 errors and 26 warnings
|
Linux x86_64 CUDA (3.10, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux x86_64 CUDA (3.11, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.14) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.14) / build
The operation was canceled.
|
|
Linux x86_64 CUDA (3.13, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux x86_64 CUDA (3.13, 12.8.1) / build
The operation was canceled.
|
|
Linux x86_64 CUDA (3.12, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux x86_64 CUDA (3.12, 12.8.1) / build
The operation was canceled.
|
|
Linux x86_64 CUDA (3.14, ft, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux x86_64 CUDA (3.14, ft, 12.8.1) / build
The operation was canceled.
|
|
Linux aarch64 (3.11) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux x86_64 CUDA (3.14, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.11) / build
The operation was canceled.
|
|
Linux x86_64 CUDA (3.14, 12.8.1) / build
The operation was canceled.
|
|
Linux aarch64 (3.14, ft) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.14, ft) / build
The operation was canceled.
|
|
Linux aarch64 (3.13, ft) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.12) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.12) / build
The operation was canceled.
|
|
Linux aarch64 (3.13, ft) / build
The operation was canceled.
|
|
Linux aarch64 (3.10) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.10) / build
The operation was canceled.
|
|
Linux aarch64 (3.13) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.13) / build
The operation was canceled.
|
|
Windows (3.14, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Windows (3.14, 12.8.1) / build
The operation was canceled.
|
|
Windows (3.14, ft, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Windows (3.14, ft, 12.8.1) / build
The operation was canceled.
|
|
Windows (3.12, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Windows (3.12, 12.8.1) / build
The operation was canceled.
|
|
Windows (3.10, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Windows (3.10, 12.8.1) / build
The operation was canceled.
|
|
Windows (3.13, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Windows (3.13, 12.8.1) / build
The operation was canceled.
|
|
Windows (3.11, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Windows (3.11, 12.8.1) / build
The operation was canceled.
|
|
Windows (3.13, ft, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Windows (3.13, ft, 12.8.1) / build
The operation was canceled.
|
|
macOS (3.14, ft) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
macOS (3.14, ft) / build
The operation was canceled.
|
|
macOS (3.10) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
macOS (3.10) / build
The operation was canceled.
|
|
macOS (3.12) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
macOS (3.12) / build
The operation was canceled.
|
|
macOS (3.14) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
macOS (3.14) / build
The operation was canceled.
|
|
Linux x86_64 CUDA (3.13, ft, 12.8.1) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux x86_64 CUDA (3.13, ft, 12.8.1) / build
The operation was canceled.
|
|
macOS (3.13, ft) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
macOS (3.13, ft) / build
The operation was canceled.
|
|
macOS (3.11) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
macOS (3.11) / build
The operation was canceled.
|
|
macOS (3.13) / build
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
macOS (3.13) / build
The operation was canceled.
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Package
Canceling since a higher priority waiting request for Package-refs/pull/1386/merge exists
|
|
Linux aarch64 (3.14) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux x86_64 CUDA (3.13, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux x86_64 CUDA (3.12, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux x86_64 CUDA (3.14, ft, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux aarch64 (3.11) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux x86_64 CUDA (3.14, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux aarch64 (3.14, ft) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux aarch64 (3.12) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux aarch64 (3.13, ft) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux aarch64 (3.10) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux aarch64 (3.13) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Windows (3.14, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Windows (3.14, ft, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Windows (3.12, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Windows (3.10, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Windows (3.13, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Windows (3.11, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Windows (3.13, ft, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
macOS (3.14, ft) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
macOS (3.10) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
macOS (3.12) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
macOS (3.14) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
Linux x86_64 CUDA (3.13, ft, 12.8.1) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
macOS (3.13, ft) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
macOS (3.11) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|
|
macOS (3.13) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@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/
|