Skip to content
Latest commit

Sorted imports #5431

Sign in to view logs

Sorted imports

Sorted imports #5431

Triggered via push February 18, 2025 16:54
@bouwewbouwew
pushed a5543cd
improve-01
Status Success
Total duration 4m 21s
Artifacts 2

verify.yml

on: push
Shellcheck
5s
Shellcheck
Dependency
4s
Dependency
Prepare
1m 5s
Prepare
Ruff check and force
13s
Ruff check and force
Check commit
36s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
23s
Process test coverage
Run mypy
22s
Run mypy
Process test complexity
13s
Process test complexity
Build and publish Python 🐍 distributions 📦 to TestPyPI
27s
Build and publish Python 🐍 distributions 📦 to TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Prepare
Cache not found for keys: 12-Linux-pre-commit-4039875599b8d9d961b9508def0b92a251155c1889098eb736989f8b3ae83396, 12-Linux-pre-commit-
Check commit
Cache not found for keys: 12-Linux-pre-commit-4039875599b8d9d961b9508def0b92a251155c1889098eb736989f8b3ae83396
Create pytest cache for Python 3.12
Cache not found for keys: 12-Linux-venv-3.12-d35f2f3719ad4680ab3b7689b8cb11e9e2523fe9cc4aa12be01f32c514a307b2-57bd198a92176cbfaa36a98427340205eddc6abc61a12d9f3d9eb44b7c065a38, 12-Linux-venv-3.12-d35f2f3719ad4680ab3b7689b8cb11e9e2523fe9cc4aa12be01f32c514a307b2-57bd198a92176cbfaa36a98427340205eddc6abc61a12d9f3d9eb44b7c065a38, 12-Linux-venv-3.12-d35f2f3719ad4680ab3b7689b8cb11e9e2523fe9cc4aa12be01f32c514a307b2, 12-Linux-venv-3.12-
Create pytest cache for Python 3.13.0
Cache not found for keys: 12-Linux-venv-3.13.0-d35f2f3719ad4680ab3b7689b8cb11e9e2523fe9cc4aa12be01f32c514a307b2-57bd198a92176cbfaa36a98427340205eddc6abc61a12d9f3d9eb44b7c065a38, 12-Linux-venv-3.13.0-d35f2f3719ad4680ab3b7689b8cb11e9e2523fe9cc4aa12be01f32c514a307b2-57bd198a92176cbfaa36a98427340205eddc6abc61a12d9f3d9eb44b7c065a38, 12-Linux-venv-3.13.0-d35f2f3719ad4680ab3b7689b8cb11e9e2523fe9cc4aa12be01f32c514a307b2, 12-Linux-venv-3.13.0-
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Artifacts

Produced during runtime
Name Size Digest
coverage-3.12 Expired
3.25 KB
sha256:1c6d7c2da41eafae1094b9affaba9f0af9a4a8ba4007c22b7abfdee90b66ca84
coverage-3.13.0 Expired
3.25 KB
sha256:3eafc584215f4027136851e51705952c12e7634878ce11f65bb02d6a7ba21778