Platform Tests #545
platform_tests-command.yml
on: schedule
setup
2s
Matrix: install
Matrix: integration_test
Annotations
16 errors and 44 warnings
|
install (ubuntu-latest, 3.9)
The process '/home/runner/miniconda3/condabin/conda' failed with exit code 1
|
|
integration_test (ubuntu-latest, 3.9)
The process '/home/runner/miniconda3/condabin/conda' failed with exit code 1
|
|
install (macos-latest, 3.9)
The process '/Users/runner/miniconda3/condabin/conda' failed with exit code 1
|
|
integration_test (macos-latest, 3.9)
The process '/Users/runner/miniconda3/condabin/conda' failed with exit code 1
|
|
install (macos-latest, 3.11)
Process completed with exit code 1.
|
|
install (macos-latest, 3.11)
Homebrew requires formulae to be in a tap, rejecting:
libomp.rb (/Users/runner/work/autogluon-assistant/autogluon-assistant/libomp.rb)
To create a tap, run e.g.
brew tap-new <user|org>/<repository>
To create a formula in a tap run e.g.
brew create <url> --tap=<user|org>/<repository>
|
|
install (macos-latest, 3.10)
Process completed with exit code 1.
|
|
install (macos-latest, 3.10)
Homebrew requires formulae to be in a tap, rejecting:
libomp.rb (/Users/runner/work/autogluon-assistant/autogluon-assistant/libomp.rb)
To create a tap, run e.g.
brew tap-new <user|org>/<repository>
To create a formula in a tap run e.g.
brew create <url> --tap=<user|org>/<repository>
|
|
integration_test (macos-latest, 3.11)
Process completed with exit code 1.
|
|
integration_test (macos-latest, 3.11)
Homebrew requires formulae to be in a tap, rejecting:
libomp.rb (/Users/runner/work/autogluon-assistant/autogluon-assistant/libomp.rb)
To create a tap, run e.g.
brew tap-new <user|org>/<repository>
To create a formula in a tap run e.g.
brew create <url> --tap=<user|org>/<repository>
|
|
integration_test (macos-latest, 3.10)
Process completed with exit code 1.
|
|
integration_test (macos-latest, 3.10)
Homebrew requires formulae to be in a tap, rejecting:
libomp.rb (/Users/runner/work/autogluon-assistant/autogluon-assistant/libomp.rb)
To create a tap, run e.g.
brew tap-new <user|org>/<repository>
To create a formula in a tap run e.g.
brew create <url> --tap=<user|org>/<repository>
|
|
integration_test (windows-latest, 3.9)
The process 'C:\Users\runneradmin\miniconda3\condabin\conda.bat' failed with exit code 1
|
|
install (windows-latest, 3.9)
The process 'C:\Users\runneradmin\miniconda3\condabin\conda.bat' failed with exit code 1
|
|
integration_test (windows-latest, 3.10)
Process completed with exit code 1.
|
|
integration_test (windows-latest, 3.11)
Process completed with exit code 1.
|
|
install (ubuntu-latest, 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (ubuntu-latest, 3.9)
CondaEnvException: Pip failed
|
|
install (ubuntu-latest, 3.9)
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'.
|
|
integration_test (ubuntu-latest, 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (ubuntu-latest, 3.9)
CondaEnvException: Pip failed
|
|
integration_test (ubuntu-latest, 3.9)
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'.
|
|
install (macos-latest, 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (macos-latest, 3.9)
CondaEnvException: Pip failed
|
|
install (macos-latest, 3.9)
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'.
|
|
integration_test (macos-latest, 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (macos-latest, 3.9)
CondaEnvException: Pip failed
|
|
integration_test (macos-latest, 3.9)
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'.
|
|
install (macos-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (macos-latest, 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'.
|
|
install (macos-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (macos-latest, 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'.
|
|
integration_test (macos-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (macos-latest, 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'.
|
|
integration_test (macos-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (macos-latest, 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'.
|
|
integration_test (windows-latest, 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (windows-latest, 3.9)
CondaEnvException: Pip failed
|
|
integration_test (windows-latest, 3.9)
ERROR: Ignored the following versions that require a different python version: 0.1.0 Requires-Python >=3.10; 0.2.0 Requires-Python >=3.10; 0.3.0 Requires-Python >=3.10; 0.3.1 Requires-Python >=3.10; 0.3.2 Requires-Python >=3.10; 0.3.3 Requires-Python >=3.10; 0.3.4 Requires-Python >=3.10; 0.3.5 Requires-Python >=3.10; 0.4.0 Requires-Python >=3.10; 0.4.1 Requires-Python >=3.10; 1.0 Requires-Python >=3.10; 1.3.0 Requires-Python >=3.10; 1.4.0a0 Requires-Python >=3.10; 1.4.0a1 Requires-Python >=3.10; 1.4.0a2 Requires-Python >=3.10; 2.0.0 Requires-Python >=3.10; 2.1.0 Requires-Python >=3.10; 2.1.1 Requires-Python >=3.10; 2.1.2 Requires-Python >=3.10; 2.10.0 Requires-Python >=3.10; 2.10.1 Requires-Python >=3.10; 2.10.2 Requires-Python >=3.10; 2.10.3 Requires-Python >=3.10; 2.10.4 Requires-Python >=3.10; 2.10.5 Requires-Python >=3.10; 2.10.6 Requires-Python >=3.10; 2.11.0 Requires-Python >=3.10; 2.11.1 Requires-Python >=3.10; 2.11.2 Requires-Python >=3.10; 2.11.3 Requires-Python >=3.10; 2.12.0 Requires-Python >=3.10; 2.12.0rc1 Requires-Python >=3.10; 2.12.1 Requires-Python >=3.10; 2.12.2 Requires-Python >=3.10; 2.12.3 Requires-Python >=3.10; 2.12.4 Requires-Python >=3.10; 2.12.5 Requires-Python >=3.10; 2.13.0 Requires-Python >=3.10; 2.13.0.1 Requires-Python >=3.10; 2.13.0.2 Requires-Python >=3.10; 2.13.0rc1 Requires-Python >=3.10; 2.13.0rc2 Requires-Python >=3.10; 2.13.0rc3 Requires-Python >=3.10; 2.13.1 Requires-Python >=3.10; 2.13.2 Requires-Python >=3.10; 2.13.3 Requires-Python >=3.10; 2.14.0 Requires-Python >=3.10; 2.14.1 Requires-Python >=3.10; 2.14.2 Requires-Python >=3.10; 2.14.3 Requires-Python >=3.10; 2.14.4 Requires-Python >=3.10; 2.14.5 Requires-Python >=3.10; 2.14.6 Requires-Python >=3.10; 2.14.7 Requires-Python >=3.10; 2.2.0 Requires-Python >=3.10; 2.2.1 Requires-Python >=3.10; 2.2.10 Requires-Python >=3.10; 2.2.2 Requires-Python >=3.10; 2.2.3 Requires-Python >=3.10; 2.2.4 Requires-Python >=3.10; 2.2.5 Requires-Python >=3.10; 2.2.6 Requires-Python >=3.10; 2.2.7 Requires-Python >=3.10; 2.2.8 Requires-Python >=3.10; 2.2.9 Requires-Python >=3.10; 2.3.0 Requires-Python >=3.10; 2.3.0rc1 Requires-Python >=3.10; 2.3.1 Requires-Python >=3.10; 2.3.2 Requires-Python >=3.10; 2.3.3 Requires-Python >=3.10; 2.3.4 Requires-Python >=3.10; 2.3.5 Requires-Python >=3.10; 2.4.0 Requires-Python >=3.10; 2.5.0 Requires-Python >=3.10; 2.5.1 Requires-Python >=3.10; 2.5.2 Requires-Python >=3.10; 2.6.0 Requires-Python >=3.10; 2.6.1 Requires-Python >=3.10; 2.7.0 Requires-Python >=3.10; 2.7.1 Requires-Python >=3.10; 2.8.0 Requires-Python >=3.10; 2.8.1 Requires-Python >=3.10; 2.9.0 Requires-Python >=3.10; 2.9.1 Requires-Python >=3.10; 2.9.2 Requires-Python >=3.10; 3.0.0 Requires-Python >=3.10; 3.0.0b1 Requires-Python >=3.10; 3.0.0b2 Requires-Python >=3.10; 3.0.0rc1 Requires-Python >=3.10; 3.0.0rc2 Requires-Python >=3.10; 3.0.0rc3 Requires-Python >=3.10; 3.0.1 Requires-Python >=3.10; 3.0.2 Requires-Python >=3.10; 3.1.0 Requires-Python >=3.10; 3.1.1 Requires-Python >=3.10; 3.2.0 Requires-Python >=3.10; 3.2.1 Requires-Python >=3.10; 3.2.2 Requires-Python >=3.10; 3.2.3 Requires-Python >=3.10; 3.2.4 Requires-Python >=3.10; 9.0.0 Requires-Python >=3.10; 9.0.1 Requires-Python >=3.10; 9.0.2 Requires-Python >=3.10; 9.0.3 Requires-Python >=3.10
ERROR: Could not find a version that satisfies the requirement fastmcp>=2.0.0 (from versions: none)
ERROR: No matching distribution found for fastmcp>=2.0.0
|
|
integration_test (windows-latest, 3.9)
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'.
|
|
install (windows-latest, 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (windows-latest, 3.9)
CondaEnvException: Pip failed
|
|
install (windows-latest, 3.9)
ERROR: Ignored the following versions that require a different python version: 0.1.0 Requires-Python >=3.10; 0.2.0 Requires-Python >=3.10; 0.3.0 Requires-Python >=3.10; 0.3.1 Requires-Python >=3.10; 0.3.2 Requires-Python >=3.10; 0.3.3 Requires-Python >=3.10; 0.3.4 Requires-Python >=3.10; 0.3.5 Requires-Python >=3.10; 0.4.0 Requires-Python >=3.10; 0.4.1 Requires-Python >=3.10; 1.0 Requires-Python >=3.10; 1.3.0 Requires-Python >=3.10; 1.4.0a0 Requires-Python >=3.10; 1.4.0a1 Requires-Python >=3.10; 1.4.0a2 Requires-Python >=3.10; 2.0.0 Requires-Python >=3.10; 2.1.0 Requires-Python >=3.10; 2.1.1 Requires-Python >=3.10; 2.1.2 Requires-Python >=3.10; 2.10.0 Requires-Python >=3.10; 2.10.1 Requires-Python >=3.10; 2.10.2 Requires-Python >=3.10; 2.10.3 Requires-Python >=3.10; 2.10.4 Requires-Python >=3.10; 2.10.5 Requires-Python >=3.10; 2.10.6 Requires-Python >=3.10; 2.11.0 Requires-Python >=3.10; 2.11.1 Requires-Python >=3.10; 2.11.2 Requires-Python >=3.10; 2.11.3 Requires-Python >=3.10; 2.12.0 Requires-Python >=3.10; 2.12.0rc1 Requires-Python >=3.10; 2.12.1 Requires-Python >=3.10; 2.12.2 Requires-Python >=3.10; 2.12.3 Requires-Python >=3.10; 2.12.4 Requires-Python >=3.10; 2.12.5 Requires-Python >=3.10; 2.13.0 Requires-Python >=3.10; 2.13.0.1 Requires-Python >=3.10; 2.13.0.2 Requires-Python >=3.10; 2.13.0rc1 Requires-Python >=3.10; 2.13.0rc2 Requires-Python >=3.10; 2.13.0rc3 Requires-Python >=3.10; 2.13.1 Requires-Python >=3.10; 2.13.2 Requires-Python >=3.10; 2.13.3 Requires-Python >=3.10; 2.14.0 Requires-Python >=3.10; 2.14.1 Requires-Python >=3.10; 2.14.2 Requires-Python >=3.10; 2.14.3 Requires-Python >=3.10; 2.14.4 Requires-Python >=3.10; 2.14.5 Requires-Python >=3.10; 2.14.6 Requires-Python >=3.10; 2.14.7 Requires-Python >=3.10; 2.2.0 Requires-Python >=3.10; 2.2.1 Requires-Python >=3.10; 2.2.10 Requires-Python >=3.10; 2.2.2 Requires-Python >=3.10; 2.2.3 Requires-Python >=3.10; 2.2.4 Requires-Python >=3.10; 2.2.5 Requires-Python >=3.10; 2.2.6 Requires-Python >=3.10; 2.2.7 Requires-Python >=3.10; 2.2.8 Requires-Python >=3.10; 2.2.9 Requires-Python >=3.10; 2.3.0 Requires-Python >=3.10; 2.3.0rc1 Requires-Python >=3.10; 2.3.1 Requires-Python >=3.10; 2.3.2 Requires-Python >=3.10; 2.3.3 Requires-Python >=3.10; 2.3.4 Requires-Python >=3.10; 2.3.5 Requires-Python >=3.10; 2.4.0 Requires-Python >=3.10; 2.5.0 Requires-Python >=3.10; 2.5.1 Requires-Python >=3.10; 2.5.2 Requires-Python >=3.10; 2.6.0 Requires-Python >=3.10; 2.6.1 Requires-Python >=3.10; 2.7.0 Requires-Python >=3.10; 2.7.1 Requires-Python >=3.10; 2.8.0 Requires-Python >=3.10; 2.8.1 Requires-Python >=3.10; 2.9.0 Requires-Python >=3.10; 2.9.1 Requires-Python >=3.10; 2.9.2 Requires-Python >=3.10; 3.0.0 Requires-Python >=3.10; 3.0.0b1 Requires-Python >=3.10; 3.0.0b2 Requires-Python >=3.10; 3.0.0rc1 Requires-Python >=3.10; 3.0.0rc2 Requires-Python >=3.10; 3.0.0rc3 Requires-Python >=3.10; 3.0.1 Requires-Python >=3.10; 3.0.2 Requires-Python >=3.10; 3.1.0 Requires-Python >=3.10; 3.1.1 Requires-Python >=3.10; 3.2.0 Requires-Python >=3.10; 3.2.1 Requires-Python >=3.10; 3.2.2 Requires-Python >=3.10; 3.2.3 Requires-Python >=3.10; 3.2.4 Requires-Python >=3.10; 9.0.0 Requires-Python >=3.10; 9.0.1 Requires-Python >=3.10; 9.0.2 Requires-Python >=3.10; 9.0.3 Requires-Python >=3.10
ERROR: Could not find a version that satisfies the requirement fastmcp>=2.0.0 (from versions: none)
ERROR: No matching distribution found for fastmcp>=2.0.0
|
|
install (windows-latest, 3.9)
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'.
|
|
install (ubuntu-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (ubuntu-latest, 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'.
|
|
install (ubuntu-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (ubuntu-latest, 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'.
|
|
integration_test (ubuntu-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (ubuntu-latest, 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'.
|
|
integration_test (ubuntu-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (ubuntu-latest, 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'.
|
|
install (windows-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (windows-latest, 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'.
|
|
integration_test (windows-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (windows-latest, 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'.
|
|
integration_test (windows-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
integration_test (windows-latest, 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'.
|
|
install (windows-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
install (windows-latest, 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'.
|