Skip to content

Weekly pre-commit autoupdate #266

Weekly pre-commit autoupdate

Weekly pre-commit autoupdate #266

Triggered via pull request March 22, 2026 13:51
Status Success
Total duration 11m 18s
Artifacts 10

conda-package-cf.yml

on: pull_request
Matrix: build_linux
Matrix: build_windows
Matrix: test_linux
Matrix: test_windows
Fit to window
Zoom out
Zoom in

Annotations

40 warnings
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.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.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'.
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.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'.
test_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/
test_windows (3.14, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.14, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_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'.
test_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/
test_windows (3.13, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.13, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_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.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/
test_windows (3.10, 2.2)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.10, 2.2)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_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'.
test_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/
test_windows (3.12, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.12, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_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'.
test_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/
test_windows (3.11, 2.3)
ERROR: 'conda activate "test_mkl_random"' exited with code 1.
test_windows (3.11, 2.3)
EnvironmentNameNotFound: Could not find conda environment: test_mkl_random You can list all discoverable environments with `conda info --envs`.
test_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'.

Artifacts

Produced during runtime
Name Size Digest
mkl_random Linux Python 3.10
374 KB
sha256:fdfabf7d6de4a6877366faead64e23cee064b9722f64031b5f1197200c89851f
mkl_random Linux Python 3.11
388 KB
sha256:7f413342b56e4f704f06d5ced479d90f48b4225f6d07022b0ed3200b564b872d
mkl_random Linux Python 3.12
381 KB
sha256:dedca1ef2f65fa456c7a263939740bad478318b9304cce0ee4d52cc176b4211d
mkl_random Linux Python 3.13
384 KB
sha256:de62d2e11f1fd6fd1dec4fa936724e53ab81ea99ca8ec173efffda3b6d9c8743
mkl_random Linux Python 3.14
386 KB
sha256:0c36d752a7454e654de009745eaa363b3c96c87e4ca8a9627cfceea047df190e
mkl_random Windows Python 3.10
302 KB
sha256:5a6ed60feed5e83a41b4db1d6eea4eb0ff454ee18762963254d72978db20462c
mkl_random Windows Python 3.11
320 KB
sha256:6f67668ce6754507e3db6dde74b073c8a8be00ad1d4d6af7f19a0712da06f2d2
mkl_random Windows Python 3.12
309 KB
sha256:b7a8b1178b9eada1360e2de55cc66709bcb4547a9b3a1a1ba4f90f77694e0724
mkl_random Windows Python 3.13
311 KB
sha256:d5e0723fa25ff23b11e05d4c31cc0f0149f2693af218aeb762e96704cb573580
mkl_random Windows Python 3.14
306 KB
sha256:b208e862b4929333a4ed537df50b3ad2ba9b98cc9d8013ae769bfe99df3a62eb