Skip to content

Update doc conf

Update doc conf #318

Triggered via push October 17, 2023 01:44
Status Failure
Total duration 16m 5s
Artifacts

ci.yml

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

Annotations

51 errors and 51 warnings
build (3.10, django>=3.2,<4.0, sqlite)
Process completed with exit code 1.
build (3.10, django>=3.2,<4.0, postgres)
Process completed with exit code 1.
build (3.10, django>=3.2,<4.0, mysql)
Process completed with exit code 1.
build (3.10, django>=4.0,<4.1, postgres)
Process completed with exit code 1.
build (3.10, django>=4.0,<4.1, sqlite)
Process completed with exit code 1.
build (3.10, django>=4.1,<4.2, postgres)
Process completed with exit code 1.
build (3.10, django>=4.1,<4.2, sqlite)
Process completed with exit code 1.
build (3.10, django>=4.1,<4.2, mysql)
Process completed with exit code 1.
build (3.10, django>=4.2,<5.0, postgres)
Process completed with exit code 1.
build (3.10, django>=4.2,<5.0, sqlite)
Process completed with exit code 1.
build (3.10, django>=4.2,<5.0, mysql)
Process completed with exit code 1.
build (3.10, django>=4.0,<4.1, mysql)
Process completed with exit code 1.
build (3.11, django>=3.2,<4.0, mysql)
Process completed with exit code 2.
build (3.11, django>=4.0,<4.1, mysql)
Process completed with exit code 2.
build (3.11, django>=3.2,<4.0, postgres)
Process completed with exit code 2.
build (3.11, django>=3.2,<4.0, sqlite)
Process completed with exit code 2.
build (3.8, django>=3.2,<4.0, mysql)
Process completed with exit code 1.
build (3.11, django>=4.0,<4.1, postgres)
Process completed with exit code 2.
build (3.7, django>=3.2,<4.0, postgres)
Process completed with exit code 1.
build (3.11, django>=4.1,<4.2, postgres)
Process completed with exit code 2.
build (3.11, django>=4.1,<4.2, mysql)
Process completed with exit code 2.
build (3.8, django>=3.2,<4.0, postgres)
Process completed with exit code 1.
build (3.7, django>=3.2,<4.0, sqlite)
Process completed with exit code 1.
build (3.11, django>=4.1,<4.2, sqlite)
Process completed with exit code 2.
build (3.11, django>=4.0,<4.1, sqlite)
Process completed with exit code 2.
build (3.8, django>=4.0,<4.1, mysql)
Process completed with exit code 1.
build (3.11, django>=4.2,<5.0, mysql)
Process completed with exit code 2.
build (3.11, django>=4.2,<5.0, postgres)
Process completed with exit code 2.
build (3.11, django>=4.2,<5.0, sqlite)
Process completed with exit code 2.
build (3.8, django>=4.0,<4.1, sqlite)
Process completed with exit code 1.
build (3.8, django>=3.2,<4.0, sqlite)
Process completed with exit code 1.
build (3.8, django>=4.1,<4.2, postgres)
Process completed with exit code 1.
build (3.8, django>=4.1,<4.2, sqlite)
Process completed with exit code 1.
build (3.8, django>=4.1,<4.2, mysql)
Process completed with exit code 1.
build (3.8, django>=4.2,<5.0, postgres)
Process completed with exit code 1.
build (3.8, django>=4.2,<5.0, mysql)
Process completed with exit code 1.
build (3.9, django>=3.2,<4.0, mysql)
Process completed with exit code 1.
build (3.9, django>=3.2,<4.0, postgres)
Process completed with exit code 1.
build (3.8, django>=4.2,<5.0, sqlite)
Process completed with exit code 1.
build (3.9, django>=4.0,<4.1, sqlite)
Process completed with exit code 1.
build (3.9, django>=4.0,<4.1, postgres)
Process completed with exit code 1.
build (3.9, django>=3.2,<4.0, sqlite)
Process completed with exit code 1.
build (3.9, django>=4.0,<4.1, mysql)
Process completed with exit code 1.
build (3.9, django>=4.1,<4.2, sqlite)
Process completed with exit code 1.
build (3.9, django>=4.1,<4.2, postgres)
Process completed with exit code 1.
build (3.9, django>=4.2,<5.0, mysql)
Process completed with exit code 1.
build (3.9, django>=4.1,<4.2, mysql)
Process completed with exit code 1.
build (3.7, django>=3.2,<4.0, mysql)
Process completed with exit code 1.
build (3.9, django>=4.2,<5.0, postgres)
Process completed with exit code 1.
build (3.9, django>=4.2,<5.0, sqlite)
Process completed with exit code 1.
build (3.8, django>=4.0,<4.1, postgres)
Process completed with exit code 1.
build (3.10, django>=3.2,<4.0, sqlite)
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/
build (3.10, django>=3.2,<4.0, postgres)
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/
build (3.10, django>=3.2,<4.0, mysql)
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/
build (3.10, django>=4.0,<4.1, postgres)
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/
build (3.10, django>=4.0,<4.1, sqlite)
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/
build (3.10, django>=4.1,<4.2, postgres)
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/
build (3.10, django>=4.1,<4.2, sqlite)
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/
build (3.10, django>=4.1,<4.2, mysql)
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/
build (3.10, django>=4.2,<5.0, postgres)
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/
build (3.10, django>=4.2,<5.0, sqlite)
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/
build (3.10, django>=4.2,<5.0, mysql)
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/
build (3.10, django>=4.0,<4.1, mysql)
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/
build (3.11, django>=3.2,<4.0, mysql)
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/
build (3.11, django>=4.0,<4.1, mysql)
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/
build (3.11, django>=3.2,<4.0, postgres)
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/
build (3.11, django>=3.2,<4.0, sqlite)
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/
build (3.8, django>=3.2,<4.0, mysql)
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/
build (3.11, django>=4.0,<4.1, postgres)
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/
build (3.7, django>=3.2,<4.0, postgres)
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/
build (3.11, django>=4.1,<4.2, postgres)
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/
build (3.11, django>=4.1,<4.2, mysql)
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/
build (3.8, django>=3.2,<4.0, postgres)
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/
build (3.7, django>=3.2,<4.0, sqlite)
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/
build (3.11, django>=4.1,<4.2, sqlite)
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/
build (3.11, django>=4.0,<4.1, sqlite)
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/
build (3.8, django>=4.0,<4.1, mysql)
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/
build (3.11, django>=4.2,<5.0, mysql)
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/
build (3.11, django>=4.2,<5.0, postgres)
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/
build (3.11, django>=4.2,<5.0, sqlite)
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/
build (3.8, django>=4.0,<4.1, sqlite)
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/
build (3.8, django>=3.2,<4.0, sqlite)
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/
build (3.8, django>=4.1,<4.2, postgres)
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/
build (3.8, django>=4.1,<4.2, sqlite)
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/
build (3.8, django>=4.1,<4.2, mysql)
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/
build (3.8, django>=4.2,<5.0, postgres)
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/
build (3.8, django>=4.2,<5.0, mysql)
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/
build (3.9, django>=3.2,<4.0, mysql)
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/
build (3.9, django>=3.2,<4.0, postgres)
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/
build (3.8, django>=4.2,<5.0, sqlite)
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/
build (3.9, django>=4.0,<4.1, sqlite)
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/
build (3.9, django>=4.0,<4.1, postgres)
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/
build (3.9, django>=3.2,<4.0, sqlite)
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/
build (3.9, django>=4.0,<4.1, mysql)
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/
build (3.9, django>=4.1,<4.2, sqlite)
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/
build (3.9, django>=4.1,<4.2, postgres)
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/
build (3.9, django>=4.2,<5.0, mysql)
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/
build (3.9, django>=4.1,<4.2, mysql)
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/
build (3.7, django>=3.2,<4.0, mysql)
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/
build (3.9, django>=4.2,<5.0, postgres)
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/
build (3.9, django>=4.2,<5.0, sqlite)
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/
build (3.8, django>=4.0,<4.1, postgres)
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/