Skip to content
Kubernetes Python Client - Validation

Update durationpy requirement from >=0.7 to >=0.10 #1836

Sign in to view logs

Update durationpy requirement from >=0.7 to >=0.10

Update durationpy requirement from >=0.7 to >=0.10 #1836

Triggered via push April 22, 2026 02:02
@dependabotdependabot[bot]
pushed 0d75d8f
dependabot/pip/durationpy-gte-0.10
Status Failure
Total duration 32s
Artifacts –

test.yaml

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

Annotations

8 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.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.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.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.8)
The strategy configuration was canceled because "build._3_10" failed
build (3.8)
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.