Skip to content

Upgrade Django to 4.2 LTS #150

Upgrade Django to 4.2 LTS

Upgrade Django to 4.2 LTS #150

Triggered via pull request September 26, 2023 09:28
Status Failure
Total duration 1m 58s
Artifacts

ci.yml

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

Annotations

3 errors and 5 warnings
build (django32, 3.8, mysql80)
Process completed with exit code 1.
build (django32, 3.8, mysql57)
The operation was canceled.
build (django42, 3.8, mysql80)
The operation was canceled.
build (quality, 3.8, mysql57)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (quality, 3.8, mysql80)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (django32, 3.8, mysql80)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (django32, 3.8, mysql57)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (django42, 3.8, mysql80)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/