Skip to content
Latest commit

Add missing starting-f #5417

Sign in to view logs

Add missing starting-f

Add missing starting-f #5417

Triggered via push February 17, 2025 19:28
@bouwewbouwew
pushed 6c1fc6a
redo-xml
Status Success
Total duration 4m 16s
Artifacts 2

verify.yml

on: push
Shellcheck
4s
Shellcheck
Dependency
3s
Dependency
Prepare
58s
Prepare
Ruff check and force
12s
Ruff check and force
Check commit
45s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
28s
Process test coverage
Run mypy
23s
Run mypy
Process test complexity
18s
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:5c32362e7a6d9ce8934584013789f9b39cca84aec133cebc17628d528d2a28d9
coverage-3.13.0 Expired
3.25 KB
sha256:7c3b49bcc6352945c453a5424de042422a3d433c6bd8f8013ac5bc0e15734d18