Skip to content

Bump django from 3.2.20 to 3.2.23 in /webapp/webapp #823

Bump django from 3.2.20 to 3.2.23 in /webapp/webapp

Bump django from 3.2.20 to 3.2.23 in /webapp/webapp #823

Triggered via pull request November 2, 2023 22:13
Status Success
Total duration 13m 11s
Artifacts

main.yml

on: pull_request
Matrix: build
publish-to-test-pypi
0s
publish-to-test-pypi
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
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.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.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/
build (3.11)
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/