🔀 PR 820 triggered by: pull_request of refs/pull/820/merge branch (workflow run ID: 24324507464; number: 4503; attempt: 1) #4503
julianz-ci-cd.yml
on: pull_request
⚙️ Pre-set global build settings
15s
👷📝 v11.1.3.dev100+gdd4c6616 changelog [mode: test]
41s
📦 v11.1.3.dev100+gdd4c6616 [mode: nightly]
/
Build dists under 🐍3.11
26s
Matrix: lint
Matrix: tests
📦 Publish ${{ needs.pre-setup.outputs.git-tag }} to PyPI
📦 Publish ${{ needs.pre-setup.outputs.git-tag }} to TestPyPI
🏷️ Publish post-release Git tag for ${{ needs.pre-setup.outputs.git-tag }}
0s
🔏 Produce a GitHub-native Attestations for ${{ needs.pre-setup.outputs.git-tag }}
0s
🏷️ Publish a GitHub Release for ${{ needs.pre-setup.outputs.git-tag }}
0s
Annotations
100 errors and 30 warnings
|
🧹 Linters / linkcheck-docs@🐍3.11
3.12
3.14@💻ubuntu-latest
Process completed with exit code 1.
|
|
🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04-arm
DEPRECATION: --no-python-version-warning is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to remove the flag as it's a no-op. Discussion can be found at https://github.com/pypa/pip/issues/13154
|
|
🧪 Tests / 🧪 🐍3.14 @ macos-15
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.8 @ macos-15-intel
getaddrinfo ENOTFOUND raw.githubusercontent.com
|
|
🧪 Tests / 🧪 🐍3.14 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.8 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.13 @ macos-15-intel
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.13 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.14 @ macos-15-intel
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.14 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.8 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.8 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.8 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.13 @ macos-15
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.13 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍pypy-3.11 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍pypy-3.11 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.12 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.12 @ macos-15-intel
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.10 @ macos-15
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.11 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.11 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.12 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.11 @ macos-15
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.11 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍pypy-3.11 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.9 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.10 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.11 @ macos-15-intel
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.9 @ macos-15-intel
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.9 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.9 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15-intel
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.14 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.14 @ ubuntu-24.04-arm
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.10 @ macos-15-intel
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.10 @ macos-15-intel
A task was canceled.
|
|
🧪 Tests / 🧪 🐍3.11 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.11 @ ubuntu-24.04-arm
A task was canceled.
|
|
🧪 Tests / 🧪 🐍3.13 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.10 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.13 @ ubuntu-24.04-arm
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.10 @ windows-2022
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.9 @ macos-15
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.13 @ windows-2022
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.13 @ windows-2022
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.14 @ windows-2025
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.14 @ windows-2025
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2025
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2025
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.12 @ windows-2025
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.12 @ windows-2025
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.10 @ windows-2025
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.10 @ windows-2025
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.9 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.9 @ ubuntu-24.04-arm
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.8 @ windows-2025
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.8 @ windows-2025
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.14 @ ubuntu-22.04
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.14 @ ubuntu-22.04
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.10 @ ubuntu-24.04-arm
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.10 @ ubuntu-24.04-arm
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.9 @ windows-2025
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.9 @ windows-2025
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.8 @ macos-15
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪 Tests / 🧪 🐍3.8 @ macos-15
The operation was canceled.
|
|
🧪 Tests / 🧪 🐍3.8 @ macos-15
DEPRECATION: --no-python-version-warning is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to remove the flag as it's a no-op. Discussion can be found at https://github.com/pypa/pip/issues/13154
|
|
check
Process completed with exit code 1.
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
🧪
The strategy configuration was canceled because "tests._3_8_macos-15-intel_py_fa" failed
|
|
⚙️ Pre-set global build settings
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5. 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/
|
|
👷📝 v11.1.3.dev100+gdd4c6616 changelog [mode: test]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4.1.1, actions/setup-python@v5, actions/upload-artifact@v4. 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/
|
|
📦 v11.1.3.dev100+gdd4c6616 [mode: nightly] / Build dists under 🐍3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/upload-artifact@v4. 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/
|
|
🧹 Linters / metadata-validation@🐍3.11
3.12
3.14@💻ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧹 Linters / doctest-docs@🐍3.11
3.12
3.14@💻ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. 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/
|
|
🧹 Linters / spellcheck-docs@🐍3.11
3.12
3.14@💻ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. 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/
|
|
🧹 Linters / build-docs@🐍3.11
3.12
3.14@💻ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. 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/
|
|
🧪 Tests / 🧪 🐍3.10 @ ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧹 Linters / linkcheck-docs@🐍3.11
3.12
3.14@💻ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. 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/
|
|
🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.12 @ macos-15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.13 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.11 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.14 @ ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧪 Tests / 🧪 🐍3.13 @ ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. 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/
|
|
🧪 Tests / 🧪 🐍3.10 @ windows-2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. 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/
|
|
🧪 Tests / 🧪 🐍3.9 @ macos-15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. 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/
|
|
🧪 Tests / 🧪 🐍3.13 @ windows-2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.14 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧪 Tests / 🧪 🐍3.12 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.10 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. 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/
|
|
🧪 Tests / 🧪 🐍3.9 @ ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧪 Tests / 🧪 🐍3.8 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧪 Tests / 🧪 🐍3.14 @ ubuntu-22.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧪 Tests / 🧪 🐍3.10 @ ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧪 Tests / 🧪 🐍3.9 @ windows-2025
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧪 Tests / 🧪 🐍3.8 @ macos-15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4, actions/download-artifact@v6. 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/
|
|
🧹 Linters / pre-commit@🐍3.11
3.12
3.14@💻ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
changelog
|
7.28 KB |
sha256:e972320fb2e337ec508f7c36e2e240a67aa03cbb4080fbe5357fe255b04b3ac4
|
|
|
python-package-distributions
|
296 KB |
sha256:7701ff70dafa7ffbbe3c781f551b0cd3a44e1de04b16980fa9b3e5b64625e4b7
|
|