Skip to content

⬆️ Bump django from 4.1.13 to 4.2.16 in /example #128

⬆️ Bump django from 4.1.13 to 4.2.16 in /example

⬆️ Bump django from 4.1.13 to 4.2.16 in /example #128

Triggered via pull request October 27, 2024 13:56
Status Success
Total duration 32s
Artifacts

ci-cd.yml

on: pull_request
Matrix: Testing Django REST Simple API Key
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Testing Django REST Simple API Key (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/
Testing Django REST Simple API Key (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. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Testing Django REST Simple API Key (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/
Testing Django REST Simple API Key (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/