Weekly pre-commit autoupdate #766
antonwolfyconda-package-cf.yml
on: pull_request
Matrix: build_linux
Matrix: build_windows
Matrix: test_linux
Matrix: test_windows
Annotations
40 warnings
|
build_windows (3.11, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
build_windows (3.11, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.11, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.11, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
build_windows (3.10, 2.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
build_windows (3.10, 2.2)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.10, 2.2)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.10, 2.2)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
build_windows (3.12, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
build_windows (3.12, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.12, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.12, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
build_windows (3.14, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
build_windows (3.14, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.14, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.14, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
build_windows (3.13, 2.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
build_windows (3.13, 2.3)
ERROR: 'conda activate "build"' exited with code 1.
|
|
build_windows (3.13, 2.3)
EnvironmentNameNotFound: Could not find conda environment: build
You can list all discoverable environments with `conda info --envs`.
|
|
build_windows (3.13, 2.3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
test_windows (3.11, numpy">=2", false, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
test_windows (3.11, numpy">=2", false, windows-latest)
ERROR: 'conda activate "test_mkl_fft"' exited with code 1.
|
|
test_windows (3.11, numpy">=2", false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_fft
You can list all discoverable environments with `conda info --envs`.
|
|
test_windows (3.11, numpy">=2", false, windows-latest)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
test_windows (3.10, numpy">=2", false, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
test_windows (3.10, numpy">=2", false, windows-latest)
ERROR: 'conda activate "test_mkl_fft"' exited with code 1.
|
|
test_windows (3.10, numpy">=2", false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_fft
You can list all discoverable environments with `conda info --envs`.
|
|
test_windows (3.10, numpy">=2", false, windows-latest)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
test_windows (3.14, numpy">=2", false, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
test_windows (3.14, numpy">=2", false, windows-latest)
ERROR: 'conda activate "test_mkl_fft"' exited with code 1.
|
|
test_windows (3.14, numpy">=2", false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_fft
You can list all discoverable environments with `conda info --envs`.
|
|
test_windows (3.14, numpy">=2", false, windows-latest)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
test_windows (3.13, numpy">=2", false, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
test_windows (3.13, numpy">=2", false, windows-latest)
ERROR: 'conda activate "test_mkl_fft"' exited with code 1.
|
|
test_windows (3.13, numpy">=2", false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_fft
You can list all discoverable environments with `conda info --envs`.
|
|
test_windows (3.13, numpy">=2", false, windows-latest)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
|
test_windows (3.12, numpy">=2", false, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: conda-incubator/setup-miniconda@fc2d68f6413eb2d87b895e92f8584b5b94a10167. 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/
|
|
test_windows (3.12, numpy">=2", false, windows-latest)
ERROR: 'conda activate "test_mkl_fft"' exited with code 1.
|
|
test_windows (3.12, numpy">=2", false, windows-latest)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_fft
You can list all discoverable environments with `conda info --envs`.
|
|
test_windows (3.12, numpy">=2", false, windows-latest)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
mkl_fft Linux Python 3.10
|
158 KB |
sha256:3635e462ef9b3c065932ce2f09a2071e7228d6708ea2ec8725d5fe6c5424bd3a
|
|
|
mkl_fft Linux Python 3.11
|
183 KB |
sha256:e896c1ce7a13f222bbd82d04f02e631f293ce6e17a3c7fb874eed28cc471e9e4
|
|
|
mkl_fft Linux Python 3.12
|
179 KB |
sha256:867b1008f73b6f89a4473deac8227757d61d4dd5f508bc032b32ebfce7486b11
|
|
|
mkl_fft Linux Python 3.13
|
178 KB |
sha256:43317c9d5623850452e964639587183d95ffb93b604b102f0cad0e7d08f6021b
|
|
|
mkl_fft Linux Python 3.14
|
179 KB |
sha256:0a822d42c6c1501a5f0976b10f740532e0015e2aa296cc6b66ae7a3867bda0f1
|
|
|
mkl_fft Windows Python 3.10
|
144 KB |
sha256:68f88bbe0de9c2baa244b0408d43a20a67dfdfe74bfaf0ac7d700b2301186790
|
|
|
mkl_fft Windows Python 3.11
|
169 KB |
sha256:32ed1c1d4a7ac39b55139bd34d9c64387ae43f80d76ff1cc3a15cf973491f827
|
|
|
mkl_fft Windows Python 3.12
|
163 KB |
sha256:8dd0cdf827d53c640e18d13b2d506e6f1e68ee17a55760de986c6548c9e90412
|
|
|
mkl_fft Windows Python 3.13
|
164 KB |
sha256:fb9aee8bb1dcdf30ba134c1b2eff123865f631215e0d90ce7099f5a5e87a32aa
|
|
|
mkl_fft Windows Python 3.14
|
165 KB |
sha256:eb8780c311a0643af1bddc34be3a5001aa10d676446b07075814050352fef711
|
|