Skip to content
Latest commit

Update CHANGELOG #5434

Sign in to view logs

Update CHANGELOG

Update CHANGELOG #5434

Triggered via push February 18, 2025 17:20
@bouwewbouwew
pushed c633ef5
improve-01
Status Success
Total duration 4m 11s
Artifacts 2

verify.yml

on: push
Shellcheck
5s
Shellcheck
Dependency
6s
Dependency
Prepare
58s
Prepare
Ruff check and force
13s
Ruff check and force
Check commit
42s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
23s
Process test coverage
Run mypy
20s
Run mypy
Process test complexity
13s
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-4039875599b8d9d961b9508def0b92a251155c1889098eb736989f8b3ae83396, 12-Linux-pre-commit-
Check commit
Cache not found for keys: 12-Linux-pre-commit-4039875599b8d9d961b9508def0b92a251155c1889098eb736989f8b3ae83396
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:6b7eb9c54f797420aec69a0ab6db1c21edc042f07d3b431e3b09211bfea8b680
coverage-3.13.0 Expired
3.25 KB
sha256:c7ca42d3f7c48e85ca023d400ae9450fa456572c4a539c9d8503dd937b09a2e9