Skip to content

Merge pull request #108 from IntelPython/bot/pre-commit-autoupdate #267

Merge pull request #108 from IntelPython/bot/pre-commit-autoupdate

Merge pull request #108 from IntelPython/bot/pre-commit-autoupdate #267

Triggered via push March 22, 2026 14:08
Status Success
Total duration 11m 7s
Artifacts 10
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.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.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.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.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.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'.
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.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.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.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
372 KB
sha256:485087be44ec75ab8674d61fc2be23b7e0738e44abfd882dc7745b0fb665ca25
mkl_random Linux Python 3.11
391 KB
sha256:01018a70790863e11b63641c40bcfda5018f87dd12f4a0a30951cf90b93fe9a5
mkl_random Linux Python 3.12
379 KB
sha256:8273c542172479022c043baccb3d6ccd9cb607da00f47de82c742d5a0db7a285
mkl_random Linux Python 3.13
383 KB
sha256:d44537b10d46b147d43d813ae72bd314647ebd6ee4765d2b73f9dfd20ce8e981
mkl_random Linux Python 3.14
386 KB
sha256:5aa9787d578d93f55768a0f7a12dc99568a8a6d967cb8e0688b42a6ec6593814
mkl_random Windows Python 3.10
302 KB
sha256:8f88103ddb38f655d483af147eb65023047ed611da3a5ef35901e4d077cb42bd
mkl_random Windows Python 3.11
323 KB
sha256:5a77a8ecfc1cb3e6d906df84c99025312da53600bb2c8599cd350b399846ee5c
mkl_random Windows Python 3.12
305 KB
sha256:f57557765dce9aada5831a65f2a89d8df7ef02e8536fdcf8088381513f594181
mkl_random Windows Python 3.13
310 KB
sha256:138caaffa5330b28e817a8f8d03cc8b8fafabd7124b27ed92ba7febf9406bd90
mkl_random Windows Python 3.14
306 KB
sha256:bd04b39645c2c54e6e2067f7d5c04f9e7c3c86bfd14a703e9033815f6eddc62b