Skip to content

Update setuptools requirement from >=21.0.0 to >=82.0.1 #1839

Update setuptools requirement from >=21.0.0 to >=82.0.1

Update setuptools requirement from >=21.0.0 to >=82.0.1 #1839

Triggered via pull request April 22, 2026 02:03
Status Failure
Total duration 25s
Artifacts

test.yaml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

10 errors
build (3.10)
The actions actions/checkout@v6, actions/setup-python@v6, and codecov/codecov-action@v6 are not allowed in kubernetes-client/python because all actions must be pinned to a full-length commit SHA.
build (3.13)
The actions actions/checkout@v6, actions/setup-python@v6, and codecov/codecov-action@v6 are not allowed in kubernetes-client/python because all actions must be pinned to a full-length commit SHA.
build (3.14)
The actions actions/checkout@v6, actions/setup-python@v6, and codecov/codecov-action@v6 are not allowed in kubernetes-client/python because all actions must be pinned to a full-length commit SHA.
build (3.9, coverage)
The actions actions/checkout@v6, actions/setup-python@v6, and codecov/codecov-action@v6 are not allowed in kubernetes-client/python because all actions must be pinned to a full-length commit SHA.
build (3.12)
The strategy configuration was canceled because "build._3_10" failed
build (3.12)
The actions actions/checkout@v6, actions/setup-python@v6, and codecov/codecov-action@v6 are not allowed in kubernetes-client/python because all actions must be pinned to a full-length commit SHA.
build (3.11)
The strategy configuration was canceled because "build._3_10" failed
build (3.11)
The actions actions/checkout@v6, actions/setup-python@v6, and codecov/codecov-action@v6 are not allowed in kubernetes-client/python because all actions must be pinned to a full-length commit SHA.
build (3.8)
The strategy configuration was canceled because "build._3_10" failed
build (3.8)
A task was canceled.