Skip to content
Latest commit

Add discord link as discussed #5413

Sign in to view logs

Add discord link as discussed

Add discord link as discussed #5413

Triggered via push February 16, 2025 16:26
@CoMPaTechCoMPaTech
pushed f656f77
dc
Status Success
Total duration 3m 59s
Artifacts 2

verify.yml

on: push
Shellcheck
6s
Shellcheck
Dependency
3s
Dependency
Prepare
55s
Prepare
Ruff check and force
18s
Ruff check and force
Check commit
36s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
18s
Process test coverage
Run mypy
19s
Run mypy
Process test complexity
14s
Process test complexity
Build and publish Python 🐍 distributions 📦 to TestPyPI
28s
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-b9c5377f92b27ce7d45ff502d3ae1f475ec362f3ac4172246e5fe6330c553477, 12-Linux-pre-commit-
Check commit
Cache not found for keys: 12-Linux-pre-commit-b9c5377f92b27ce7d45ff502d3ae1f475ec362f3ac4172246e5fe6330c553477
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:51a658a38ca9230171c66b5cf333aef51e0d57be3d64c7a7a98046b6ff010794
coverage-3.13.0 Expired
3.25 KB
sha256:e9ee2c78874bedf1bac791a3bd70ba3961ec9923c08cc3e7fe980747e3307329