Skip to content
Latest commit

Remove typing #5433

Sign in to view logs

Remove typing

Remove typing #5433

Triggered via push February 18, 2025 17:17
@bouwewbouwew
pushed 00761fb
improve-01
Status Success
Total duration 4m 9s
Artifacts 2

verify.yml

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

Annotations

5 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
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:421540b5f15e283f8a957d3ba7397755da01d09ecd7b1d0e76c5627e420cd0fd
coverage-3.13.0 Expired
3.25 KB
sha256:eac6898ba8b6365b2983bd336e50cf3391931710203c9d92b03b85abb5d1e1ea