Skip to content

[WIP] django-cms 4.1 compatible for version locking #48

[WIP] django-cms 4.1 compatible for version locking

[WIP] django-cms 4.1 compatible for version locking #48

Triggered via pull request November 7, 2024 14:36
Status Failure
Total duration 21s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 4 warnings
flake8: djangocms_version_locking/models.py#L1
'django.conf.settings' imported but unused
flake8: djangocms_version_locking/models.py#L2
'django.db.models' imported but unused
flake8: djangocms_version_locking/models.py#L3
'django.utils.translation.gettext_lazy as _' imported but unused
flake8: djangocms_version_locking/models.py#L5
'djangocms_versioning.models.Version' imported but unused
flake8
The process '/opt/hostedtoolcache/Python/3.9.20/x64/bin/flake8' failed with exit code 1
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/
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/