Skip to content

[Snyk] Security upgrade django from 3.2.25 to 4.2.16 #186

[Snyk] Security upgrade django from 3.2.25 to 4.2.16

[Snyk] Security upgrade django from 3.2.25 to 4.2.16 #186

Triggered via pull request September 4, 2024 22:44
Status Failure
Total duration 11s
Artifacts

testing.yml

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

Annotations

3 errors and 2 warnings
postgres (3.11, tcms.kiwitcms.org)
Process completed with exit code 127.
postgres (3.11, public.tenant.kiwitcms.org)
The job was canceled because "_3_11_tcms_kiwitcms_org" failed.
postgres (3.11, public.tenant.kiwitcms.org)
Process completed with exit code 127.
postgres (3.11, tcms.kiwitcms.org)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.11, tcms.kiwitcms.org)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/