Skip to content

A quick attempt at making taskproc handle migrations from one k8s clu… #295

A quick attempt at making taskproc handle migrations from one k8s clu…

A quick attempt at making taskproc handle migrations from one k8s clu… #295

Triggered via pull request July 10, 2024 17:39
Status Success
Total duration 1m 16s
Artifacts

ci.yml

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

Annotations

4 warnings
tox (tox_docs)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
tox (tox_docs)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
tox (test)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
tox (test)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/