Skip to content

Add documentation for patching utilities and interfaces #360

Add documentation for patching utilities and interfaces

Add documentation for patching utilities and interfaces #360

Triggered via pull request March 19, 2026 21:46
Status Success
Total duration 11m 36s
Artifacts 10

conda-package.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.13)
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)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.13)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.13)
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)
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)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.11)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.11)
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)
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)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.14)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.14)
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)
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)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.12)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.12)
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)
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)
ERROR: 'conda activate "build"' exited with code 1.
build_windows (3.10)
EnvironmentNameNotFound: Could not find conda environment: build You can list all discoverable environments with `conda info --envs`.
build_windows (3.10)
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.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'.
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'.

Artifacts

Produced during runtime
Name Size Digest
mkl_random Linux Python 3.10
371 KB
sha256:cfa16542af58d031875ca5f20a529cfd9334d98578ba9546369929760ba9a7b0
mkl_random Linux Python 3.11
390 KB
sha256:4b33248d9f460c0e12ad9cf8eaa8f9d28cfc42199b291b427b4ef24934dd08d8
mkl_random Linux Python 3.12
380 KB
sha256:1ba6615d8b899264320e007eb1ce35904e479a952a5a547fa372aeced8c1e89d
mkl_random Linux Python 3.13
384 KB
sha256:1e963ed4cd557591a2ad4ae71328f6b74b3ea633f28b0c782be53b75c6e535eb
mkl_random Linux Python 3.14
388 KB
sha256:0a5b047d01da1f6de5ff40a35fd685d19fa6463ff65b3f5b255ac8c3d9e295f6
mkl_random Windows Python 3.10
302 KB
sha256:bff0dfed39d6bb50c344d375b88494c98ae854cf83b091661800bf29bb490eeb
mkl_random Windows Python 3.11
320 KB
sha256:d381024e0eb4b43fe966dbdb0211b36e241785acc428aef6b83ecd68975c22f0
mkl_random Windows Python 3.12
305 KB
sha256:1fff6faee7268ddc3d20785b16a9f443814b945bb4541ce280d5a121d48e9273
mkl_random Windows Python 3.13
311 KB
sha256:4bdc38a7fd65c9e7d27ebbe86d9e71b7e360ba205de7aac228e56e4aaa45f451
mkl_random Windows Python 3.14
310 KB
sha256:587508def9e99cee317d284887cfb754d13bfe681c0a3e91dac8116cb753f71f