Skip to content
Latest commit

Alternative solution #5397

Sign in to view logs

Alternative solution

Alternative solution #5397

Triggered via push February 14, 2025 18:49
@bouwewbouwew
pushed daa5fe9
fix-issue-833
Status Success
Total duration 4m 10s
Artifacts 2

verify.yml

on: push
Shellcheck
4s
Shellcheck
Dependency
4s
Dependency
Prepare
57s
Prepare
Ruff check and force
13s
Ruff check and force
Check commit
39s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
23s
Process test coverage
Run mypy
19s
Run mypy
Process test complexity
14s
Process test complexity
Build and publish Python 🐍 distributions 📦 to TestPyPI
32s
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.24 KB
sha256:80155ec5b158e90fb9f0bd1233917e0c4f344f8eefe86a46a97a5a189e409b26
coverage-3.13.0 Expired
3.24 KB
sha256:773f184e0437b9e2d26c79479f7faa7fecc462ace69cca8cd997d1d569030ae0