Skip to content

feat: upgrade to Django 4.2 (#226) #270

feat: upgrade to Django 4.2 (#226)

feat: upgrade to Django 4.2 (#226) #270

Triggered via push July 21, 2023 14:15
Status Success
Total duration 1m 10s
Artifacts

ci.yml

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

Annotations

4 warnings
Tests (ubuntu-20.04, 3.8, django32)
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/
Tests (ubuntu-20.04, 3.8, django42)
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/
Tests (ubuntu-20.04, 3.8, quality)
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/
Tests (ubuntu-20.04, 3.8, 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/