Skip to content

pip-tools

pip-tools #1897

Triggered via schedule June 14, 2026 03:41
Status Failure
Total duration 56s
Artifacts 9

pip-tools.yml

on: schedule
Matrix: deps
check ⮸ everything
3s
check ⮸ everything
Open/refresh a PR
0s
Open/refresh a PR
Fit to window
Zoom out
Zoom in

Annotations

55 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.14 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.13 @ 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-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.11 @ ubuntu-24.04-arm
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
⛓🔒 🐍pypy-3.11 @ macOS-15
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
⛓🔒 🐍3.12 @ windows-2022
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.10 @ macOS-15
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
⛓🔒 🐍3.9 @ 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.15.0-0 @ windows-2022
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.9 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.11 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.11 @ windows-2022
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.9 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.9 @ 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
A task was canceled.
⛓🔒 🐍3.8 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.8 @ ubuntu-24.04-arm
The operation 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.
⛓🔒 🐍~3.15.0-0 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍~3.15.0-0 @ ubuntu-24.04-arm
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.9 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.9 @ windows-2022
The operation was canceled.
⛓🔒 🐍3.11 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.11 @ ubuntu-22.04
The operation was canceled.
⛓🔒 🐍3.14 @ ubuntu-24.04-arm
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.14 @ ubuntu-24.04-arm
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.13 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.13 @ windows-2022
The operation was canceled.
⛓🔒 🐍~3.15.0-0 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍~3.15.0-0 @ macOS-15-intel
The operation was canceled.
⛓🔒 🐍3.8 @ macOS-15-intel
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.8 @ macOS-15-intel
The operation was canceled.
⛓🔒 🐍pypy-3.11 @ ubuntu-22.04
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍pypy-3.11 @ ubuntu-22.04
The operation was canceled.
⛓🔒 🐍3.10 @ windows-2022
The strategy configuration was canceled because "deps._3_14_windows-2022" failed
⛓🔒 🐍3.10 @ windows-2022
The operation was canceled.
check ⮸ everything
Process completed with exit code 1.
⛓🔒 🐍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 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/
⛓🔒 🐍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 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/
⛓🔒 🐍3.11 @ 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 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/
⛓🔒 🐍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 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/
⛓🔒 🐍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 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/
⛓🔒 🐍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, 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 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/
⛓🔒 🐍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/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 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/
⛓🔒 🐍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 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/
⛓🔒 🐍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. 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/
⛓🔒 🐍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, fregante/setup-git-user@v1.1.0. 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/
⛓🔒 🐍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 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/
⛓🔒 🐍~3.15.0-0 @ 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, fregante/setup-git-user@v1.1.0. 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/
⛓🔒 🐍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 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/
⛓🔒 🐍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 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/
⛓🔒 🐍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/checkout@v3, 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/
⛓🔒 🐍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/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 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/
⛓🔒 🐍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 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/
⛓🔒 🐍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. 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/
⛓🔒 🐍~3.15.0-0 @ macOS-15-intel
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 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/
⛓🔒 🐍3.8 @ macOS-15-intel
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 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/
⛓🔒 🐍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/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 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/
⛓🔒 🐍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, fregante/setup-git-user@v1.1.0. 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/

Artifacts

Produced during runtime
Name Size Digest
pip-constraints-git-patches--219ac629-1bdb-4c9a-ba3a-26fcdc29f3c1 Expired
1.54 KB
sha256:69ca6e2226640c7ff98bb602b1db041be60d0e7b6075444d7fd009ba9581ceaf
pip-constraints-git-patches--58dc9003-77c4-406e-8f77-3e4f8552b1e7 Expired
1.53 KB
sha256:9d96fe4c719d1abc562129de13843b10326d16b3a64519faab38ebec756acfa2
pip-constraints-git-patches--5c887ae2-3bf1-4f70-b4e2-963fac031a80 Expired
1.53 KB
sha256:227369eebe01e2c71a2ddee6e9fc127f4620abf73198da9df530bde67235d131
pip-constraints-git-patches--714a1bd8-ad48-4630-9fd0-0fe83d26f9c2 Expired
1.55 KB
sha256:5d3d79e28f43cddda034f3c9d76e04707f6c514d8bea6337776e5747fe049204
pip-constraints-git-patches--9b0b65d2-307f-452c-818e-296dfca347f6 Expired
1.56 KB
sha256:95448a7ff5c683326551af6f362051172475a6d9c2c0a8d5fcebed5357a00dcc
pip-constraints-git-patches--e99a5ba1-9cab-4806-aef5-2a47c42d3eaf Expired
1.61 KB
sha256:fe10089f509f77b47a11764fdce25a967c84cfb53e168fb8a543202d7db6c012
pip-constraints-git-patches--f22d955d-c88b-4956-ae53-72fb6f058df1 Expired
1.56 KB
sha256:14a9b68e894ad9a6fce29c3dac5ddad34dac23ebdd0b782a5383a11f6c6d4b5c
pip-constraints-git-patches--f648de67-58bd-4aea-b64a-9d910a62b004 Expired
1.53 KB
sha256:478c3b67e970658486a7ea6bf68fffa0bd67242210e088fff512015011fce3d7
pip-constraints-git-patches--f95f7283-e942-49bd-b6ef-b4c471dd43e3 Expired
1.54 KB
sha256:9f338b8fd9738d5141dbae7248bc32152b5a7b674a346506595731a6081ca333