Skip to content
Latest commit

Bump to a3 #5401

Sign in to view logs

Bump to a3

Bump to a3 #5401

Triggered via push February 15, 2025 11:55
@bouwewbouwew
pushed bb2acba
fix-issue-833
Status Success
Total duration 4m 4s
Artifacts 2

verify.yml

on: push
Shellcheck
5s
Shellcheck
Dependency
6s
Dependency
Prepare
1m 3s
Prepare
Ruff check and force
14s
Ruff check and force
Check commit
36s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
17s
Process test coverage
Run mypy
17s
Run mypy
Process test complexity
13s
Process test complexity
Build and publish Python 🐍 distributions 📦 to TestPyPI
30s
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:77d8fca11ac26d956fed8dfa209f2aa0ec838d1d3d2853c81721bbd03e199e01
coverage-3.13.0 Expired
3.24 KB
sha256:ba77f41b5b7696deff74ef877a7ceed76a67f35315ae99bce9659d0031fdbe7e