Skip to content

Feat: Migrate to Django CMS 4.1 compatible #5

Feat: Migrate to Django CMS 4.1 compatible

Feat: Migrate to Django CMS 4.1 compatible #5

Triggered via pull request August 21, 2024 11:17
Status Success
Total duration 21s
Artifacts

linting.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
flake8
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, liskin/gh-problem-matcher-wrap@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
flake8
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, liskin/gh-problem-matcher-wrap@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
isort
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, liskin/gh-problem-matcher-wrap@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
isort
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, liskin/gh-problem-matcher-wrap@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/