Skip to content

chore: upgrade Django to 4.2.16 #355

chore: upgrade Django to 4.2.16

chore: upgrade Django to 4.2.16 #355

Triggered via pull request September 3, 2024 16:52
Status Success
Total duration 1m 5s
Artifacts

migrations-mysql8-check.yml

on: pull_request
Matrix: check migrations
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
check migrations (ubuntu-20.04, 3.12)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check migrations (ubuntu-20.04, 3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check migrations (ubuntu-20.04, 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, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check migrations (ubuntu-20.04, 3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/