🌃 Nightly run of Commit 2ffb0baf8aa480da9da8d522b3fd7eab271f6dba triggered by: schedule of refs/heads/main branch (workflow run ID: 27087345560; number: 479; attempt: 1) #479
webknjazscheduled-runs.yml
on: schedule
🧪 Main CI/CD pipeline
/
⚙️ Pre-set global build settings
10s
🧪 Main CI/CD pipeline
/
👷📝 v11.1.3.dev87+g2ffb0baf changelog [mode: test]
36s
🧪 Main CI/CD pipeline
/
...
/
Build dists under 🐍3.11
34s
Matrix: 🧪 Main CI/CD pipeline / lint
Matrix: 🧪 Main CI/CD pipeline / tests
🧪 Main CI/CD pipeline
/
📦 Publish ${{ needs.pre-setup.outputs.git-tag }} to PyPI
🧪 Main CI/CD pipeline
/
📦 Publish ${{ needs.pre-setup.outputs.git-tag }} to TestPyPI
🧪 Main CI/CD pipeline
/
🏷️ Publish post-release Git tag for ${{ needs.pre-setup.outputs.git-tag }}
🧪 Main CI/CD pipeline
/
🔏 Produce a GitHub-native Attestations for ${{ needs.pre-setup.outputs.git-tag }}
0s
🧪 Main CI/CD pipeline
/
🏷️ Publish a GitHub Release for ${{ needs.pre-setup.outputs.git-tag }}
0s
Annotations
110 errors, 28 warnings, and 6 notices
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ ubuntu-24.04-arm
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ ubuntu-24.04-arm
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ windows-2025
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ windows-2025
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍pypy-3.11 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍pypy-3.11 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.10 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ ubuntu-22.04
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ ubuntu-22.04
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.10 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.10 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.10 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.10 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.10 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.10 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04-arm
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ ubuntu-24.04-arm
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ ubuntu-24.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15-intel
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ windows-2022
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ windows-2022
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ ubuntu-22.04
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ ubuntu-24.04-arm
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ windows-2025
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ macos-15
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15
A task was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15
WARNING: Cache entry deserialization failed, entry ignored
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15
WARNING: Cache entry deserialization failed, entry ignored
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ windows-2025
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ windows-2025
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍pypy-3.11 @ ubuntu-22.04
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍pypy-3.11 @ ubuntu-22.04
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2025
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ windows-2025
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ windows-2025
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ ubuntu-24.04-arm
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ ubuntu-24.04-arm
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ macos-15
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ macos-15
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ macos-15
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ macos-15
The operation was canceled.
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ macos-15
WARNING: Cache entry deserialization failed, entry ignored
|
|
🧪 Main CI/CD pipeline / 🧹 Linters / pre-commit@🐍3.11
3.12
3.14@💻ubuntu-latest
Process completed with exit code 1.
|
|
🧪 Main CI/CD pipeline / check
Process completed with exit code 1.
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
⏳
The strategy configuration was canceled because "main-ci-cd-pipeline.tests._3_11_ubuntu-24_04-arm_py" failed
|
|
🧪 Main CI/CD pipeline / ⚙️ 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 👷📝 v11.1.3.dev87+g2ffb0baf 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 📦 v11.1.3.dev87+g2ffb0baf [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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧹 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧹 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧹 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧹 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧹 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ 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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, test-summary/action@v2.3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ macos-15
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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍pypy-3.11 @ 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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.13 @ 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧹 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 16th, 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/
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.14 @ windows-2025
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.8 @ windows-2025
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.12 @ windows-2025
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.9 @ windows-2025
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍~3.15.0-0 @ windows-2025
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
🧪 Main CI/CD pipeline / 🧪 Tests / 🧪 🐍3.11 @ windows-2025
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
changelog
|
6.84 KB |
sha256:085e7b4656ce4d54af112d8d586d006d0e2c1a5f7ade38bfaaaa3e77a49f4967
|
|
|
python-package-distributions
|
291 KB |
sha256:db5aa030b920bca269db72c56781394558d89f4b0852bb65e1977594c5a3bed0
|
|