chore(deps): bump the actions group with 4 updates #3494
Annotations
9 errors and 9 warnings
|
build (3.12, >=2.1)
Response status code does not indicate success: 401 (Unauthorized).
|
|
build (3.13, >=2.1)
The strategy configuration was canceled because "build._3_12___2_1" failed
|
|
build (3.13, >=2.1)
The operation was canceled.
|
|
build (3.11, >=2.1)
The strategy configuration was canceled because "build._3_12___2_1" failed
|
|
build (3.11, >=2.1)
The operation was canceled.
|
|
build (3.13, >=2.1, zlib-ng)
The strategy configuration was canceled because "build._3_12___2_1" failed
|
|
build (3.13, >=2.1, zlib-ng)
The operation was canceled.
|
|
build (3.11, ==1.24.*)
The strategy configuration was canceled because "build._3_12___2_1" failed
|
|
build (3.11, ==1.24.*)
The operation was canceled.
|
|
build (3.12, >=2.1)
Back off 14.307 seconds before retry.
|
|
build (3.12, >=2.1)
Failed to download action 'https://api.github.com/repos/conda-incubator/setup-miniconda/tarball/fc2d68f6413eb2d87b895e92f8584b5b94a10167'. Error: Response status code does not indicate success: 401 (Unauthorized). FFC0:2312D0:AB41D7:2D3CDC4:69B24006
|
|
build (3.12, >=2.1)
Back off 18.282 seconds before retry.
|
|
build (3.12, >=2.1)
Failed to download action 'https://api.github.com/repos/conda-incubator/setup-miniconda/tarball/fc2d68f6413eb2d87b895e92f8584b5b94a10167'. Error: Response status code does not indicate success: 401 (Unauthorized). FFC0:DF01D:6F46EF:1D4F22C:69B23FF3
|
|
build (3.13, >=2.1)
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@v3.3.0. 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 (3.13, >=2.1)
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 (3.11, >=2.1)
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@v3.3.0. 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 (3.13, >=2.1, zlib-ng)
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@v3.3.0. 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 (3.11, ==1.24.*)
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@v3.3.0. 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/
|