Skip to content
Linting

Fix way to determine default_complex #756

Sign in to view logs

Fix way to determine default_complex

Fix way to determine default_complex #756

Triggered via pull request August 12, 2024 14:25
@cbourjaucbourjau
synchronize #283
cbourjau:fix-default-complex
Status Success
Total duration 1m 13s
Artifacts –

lint.yml

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

Annotations

4 warnings
build (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1, pre-commit/action@v2.0.3. 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)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v1, pre-commit/action@v2.0.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1, pre-commit/action@v2.0.3. 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)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v1, pre-commit/action@v2.0.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/