Skip to content
Django CI

fix: Added support for Django42 #261

Sign in to view logs

fix: Added support for Django42

fix: Added support for Django42 #261

Triggered via pull request September 21, 2023 15:55
@zubairshakoorarbisoftzubairshakoorarbisoft
synchronize #346
zshkoor/django42-support
Status Failure
Total duration 23m 32s
Artifacts –

ci.yml

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

Annotations

3 errors and 3 warnings
build (py38, django32, mysql57)
Process completed with exit code 2.
build (py38, django42, mysql80)
The operation was canceled.
build (py38, django32, mysql80)
The operation was canceled.
build (py38, django32, 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 (py38, django42, 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 (py38, django32, 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/