Skip to content
Latest commit

Add comment, move break to optimize #5421

Sign in to view logs

Add comment, move break to optimize

Add comment, move break to optimize #5421

Triggered via push February 18, 2025 07:35
@bouwewbouwew
pushed 90ed590
redo-xml
Status Success
Total duration 3m 50s
Artifacts 2

verify.yml

on: push
Shellcheck
3s
Shellcheck
Dependency
3s
Dependency
Prepare
56s
Prepare
Ruff check and force
16s
Ruff check and force
Check commit
34s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
18s
Process test coverage
Run mypy
18s
Run mypy
Process test complexity
14s
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

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:2ffcb3fe80a38e487b0b809135fb019667bdef4064cfef284e5a72e26b2be119
coverage-3.13.0 Expired
3.25 KB
sha256:a819dac7a871c79379e81bcc0f9d70a21e79c39f5dca2c6aab5f4c9f86b17c3c