Run unit tests, integration tests, and publish package if tagged #830
ci.yaml
on: schedule
Matrix: run-unit-and-integration-tests-with-conda-install
Matrix: test-pip-installation
format
14s
Lint with ruff
10s
Publish package
0s
Annotations
4 errors and 32 warnings
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.12)
Process completed with exit code 1.
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.10)
Process completed with exit code 1.
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.10)
Process completed with exit code 1.
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.11)
Process completed with exit code 1.
|
|
Lint with ruff
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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-pip-installation (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, actions/setup-python@v5. 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-pip-installation (macos-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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-pip-installation (macos-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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-pip-installation (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, actions/setup-python@v5. 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-pip-installation (ubuntu-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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-pip-installation (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, conda-incubator/setup-miniconda@v3. 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/
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.12)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 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'.
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.12)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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, actions/upload-artifact@v4, conda-incubator/setup-miniconda@v3. 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/
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.10)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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'.
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.10)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, conda-incubator/setup-miniconda@v3. 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/
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.12)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 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'.
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.12)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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, actions/upload-artifact@v4, conda-incubator/setup-miniconda@v3. 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/
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.10)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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'.
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.10)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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, actions/upload-artifact@v4, conda-incubator/setup-miniconda@v3. 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/
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.11)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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'.
|
|
run-unit-and-integration-tests-with-conda-install (ubuntu-latest, 3.11)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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, actions/upload-artifact@v4, conda-incubator/setup-miniconda@v3. 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/
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.11)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
|
run-unit-and-integration-tests-with-conda-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'.
|
|
run-unit-and-integration-tests-with-conda-install (macos-latest, 3.11)
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
macos-latest-3.10-example-workflow-results
|
1.99 GB |
sha256:bb28c255af7069e5010580cf2276506a1b5dc494dc3a9346bc4da3238fdaa68b
|
|
|
macos-latest-3.11-example-workflow-results
|
1.99 GB |
sha256:c66590887d0b5ceffd136472d8bcea41055ef935257fc7369541d91627730685
|
|
|
macos-latest-3.12-example-workflow-results
|
1.99 GB |
sha256:b4a1a203bc4274ed5d9cfd6a7c1cf4b0f8b694dce8d9e131350a3d39aba161f6
|
|
|
ubuntu-latest-3.10-example-workflow-results
|
3.78 GB |
sha256:0493fffb25cb7e42881119409cccea71a04df789a805fcd48ee01bb22d3c3436
|
|
|
ubuntu-latest-3.11-example-workflow-results
|
3.78 GB |
sha256:aa6459aa62bbb77924f48d125f43382ff16f91b36e7714f99ced45df8a22d684
|
|
|
ubuntu-latest-3.12-example-workflow-results
|
3.78 GB |
sha256:a3ae47c6958aa3383ee05b9d310abefc215574d43516dcc18280677b86fee7ee
|
|