Skip to content

Legacy-testing: add support for POST #5399

Legacy-testing: add support for POST

Legacy-testing: add support for POST #5399

Triggered via push February 15, 2025 10:57
Status Success
Total duration 4m 15s
Artifacts 2

verify.yml

on: push
Ruff check and force
15s
Ruff check and force
Check commit
37s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
18s
Process test coverage
Process test complexity
14s
Process test complexity
Build and publish Python 🐍 distributions 📦 to TestPyPI
28s
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:898733920a93e844b4c949d04049a87a793009f85d2bbef5fab335d56d000ba6
coverage-3.13.0 Expired
3.24 KB
sha256:05c525542de8a106305034c67b282a4e7879c11614fd19ff3d27ae1db82e3af9