Skip to content
Latest commit

Remove specific python 3.13.0 requirement #5528

Sign in to view logs

Remove specific python 3.13.0 requirement

Remove specific python 3.13.0 requirement #5528

Triggered via push April 24, 2025 06:00
@bouwewbouwew
pushed 6a6f52c
py-ver
Status Success
Total duration 3m 0s
Artifacts 2

verify.yml

on: push
Shellcheck
5s
Shellcheck
Dependency
7s
Dependency
Prepare
57s
Prepare
Ruff check and force
7s
Ruff check and force
Check commit
28s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
10s
Process test coverage
Run mypy
11s
Run mypy
Process test complexity
5s
Process test complexity
Build and publish Python 🐍 distributions 📦 to TestPyPI
18s
Build and publish Python 🐍 distributions 📦 to TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
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):
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
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.

Artifacts

Produced during runtime
Name Size Digest
coverage-3.12 Expired
3.25 KB
sha256:a60ebf21364dae813897ceaf16cc50b4fa2f2cf3af5f428395aa44739b495bf7
coverage-3.13 Expired
3.25 KB
sha256:a60ebf21364dae813897ceaf16cc50b4fa2f2cf3af5f428395aa44739b495bf7