pip-tools #1808
webknjazAnnotations
56 errors and 22 warnings
|
⛓🔒 🐍3.14 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.14 @ windows-2022
Process completed with exit code 1.
|
|
⛓🔒 🐍3.13 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.14 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.11 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.12 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.9 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍pypy-3.11 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.8 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.10 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍pypy-3.11 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.9 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍~3.15.0-0 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.10 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍~3.15.0-0 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍pypy-3.11 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.11 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.10 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍~3.15.0-0 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍~3.15.0-0 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.11 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.12 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.9 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.9 @ ubuntu-24.04-arm
A task was canceled.
|
|
⛓🔒 🐍3.8 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.8 @ macOS-15
The operation was canceled.
|
|
⛓🔒 🐍pypy-3.11 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍pypy-3.11 @ ubuntu-24.04-arm
The operation was canceled.
|
|
⛓🔒 🐍3.8 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.8 @ ubuntu-22.04
The operation was canceled.
|
|
⛓🔒 🐍3.11 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.11 @ ubuntu-24.04-arm
A task was canceled.
|
|
⛓🔒 🐍3.11 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.11 @ windows-2022
The operation was canceled.
|
|
⛓🔒 🐍3.14 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.9 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.13 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.13 @ windows-2022
Process completed with exit code 1.
|
|
⛓🔒 🐍3.10 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.10 @ windows-2022
The operation was canceled.
|
|
⛓🔒 🐍3.9 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.9 @ windows-2022
The operation was canceled.
|
|
⛓🔒 🐍pypy-3.11 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍pypy-3.11 @ windows-2022
The operation was canceled.
|
|
⛓🔒 🐍3.8 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.8 @ windows-2022
The operation was canceled.
|
|
⛓🔒 🐍~3.15.0-0 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍~3.15.0-0 @ windows-2022
The operation was canceled.
|
|
⛓🔒 🐍3.10 @ macOS-15
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.10 @ macOS-15
The operation was canceled.
|
|
⛓🔒 🐍3.12 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.12 @ ubuntu-24.04-arm
The operation was canceled.
|
|
⛓🔒 🐍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
|
|
⛓🔒 🐍3.12 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
|
|
⛓🔒 🐍3.12 @ windows-2022
The operation was canceled.
|
|
check ⮸ everything
Process completed with exit code 1.
|
|
⛓🔒 🐍3.13 @ 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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍3.8 @ 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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍3.12 @ 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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, 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/
|
|
⛓🔒 🐍pypy-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/checkout@v3, 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/
|
|
⛓🔒 🐍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/checkout@v3, 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/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, actions/upload-artifact@v4, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, 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/
|
|
⛓🔒 🐍3.9 @ windows-2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, 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/
|
|
⛓🔒 🐍pypy-3.11 @ windows-2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, 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/
|
|
⛓🔒 🐍3.8 @ windows-2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, 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/
|
|
⛓🔒 🐍~3.15.0-0 @ windows-2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, 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/
|
|
⛓🔒 🐍3.10 @ 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/checkout@v3, actions/setup-python@v5, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍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/checkout@v3, actions/setup-python@v5, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
⛓🔒 🐍3.12 @ 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/checkout@v3, actions/setup-python@v5, fregante/setup-git-user@v1.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
pip-constraints-git-patches--0c8ceee2-e644-488a-a296-1d2ff642ab50
|
1.31 KB |
sha256:2261149b9ffbde522b66c44f0b5ebca67045368fd0ed8807b47c704d058f11a0
|
|
|
pip-constraints-git-patches--355bcb04-2238-4d57-b500-5ab77927c2ba
|
1.05 KB |
sha256:b871e0cd95ad1ea8f58408467c8cf93c614ed92cc4082d7ce9f636dcb5d89b63
|
|
|
pip-constraints-git-patches--3957b22f-2dde-4fb5-a9d7-456462b4d05c
|
1.31 KB |
sha256:317b075d61426fe2545f5a875d795a6282e6b551be544499c53fa22b37a178a6
|
|
|
pip-constraints-git-patches--7a3f10f1-f463-4681-9056-5b9ebf01fbd7
|
1.31 KB |
sha256:d85934c5db224bbb967d4200acb99e9d1c343163fddaf0aa28cdc98d90b6fad7
|
|
|
pip-constraints-git-patches--8437761f-0a05-42c2-9b48-f5226477a26f
|
1.33 KB |
sha256:628cee89429589646ec3ae1d0a088a8f4c6bd68d5518e08287d3fa0e32fea522
|
|
|
pip-constraints-git-patches--8fa83002-9878-48ec-be7f-c02e59e81f66
|
1.31 KB |
sha256:7f34bc5008941890902b58bed677852730133c3b76cec518596379217e6b2559
|
|
|
pip-constraints-git-patches--af0d4641-8729-4714-adbc-f2daf5bb1007
|
1.32 KB |
sha256:9f8168b2e8b0c25659adf56bdd3ff995ae103284a3cab0001ef35f087aad49a2
|
|
|
pip-constraints-git-patches--b85d9da5-2cb0-4eb6-952a-a89e56b8daf0
|
1.31 KB |
sha256:b2848540f2c201ccb0411c3b5eea96683eace53dcb294170ef9e0536a3d38e18
|
|
|
pip-constraints-git-patches--d371e7b7-da67-43cf-850d-9bd4ff0fa528
|
1.33 KB |
sha256:cdf5baf2a2fdb35e14320b90312713fa8078b79032a5db254a0dc787534260ae
|
|