Skip to content
Python CI

add support for Django 4.2 storages (Django 5.1 support) #76

Sign in to view logs

add support for Django 4.2 storages (Django 5.1 support)

add support for Django 4.2 storages (Django 5.1 support) #76

Re-run triggered November 16, 2023 16:30
@jriefjrief
#626
PetrDlouhy:django42_storages
Status Success
Total duration 1m 34s
Artifacts –

python.yml

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

Annotations

4 warnings
build (3.10)
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/
build (3.9)
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/
build (3.7)
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/
build (3.8)
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/