Skip to content

Update pre-commit hook PyCQA/bandit to v1.8.3 #5419

Update pre-commit hook PyCQA/bandit to v1.8.3

Update pre-commit hook PyCQA/bandit to v1.8.3 #5419

Triggered via push February 18, 2025 02:31
Status Success
Total duration 4m 16s
Artifacts 2

verify.yml

on: push
Ruff check and force
13s
Ruff check and force
Check commit
35s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
28s
Process test coverage
Process test complexity
18s
Process test complexity
Build and publish Python 🐍 distributions 📦 to TestPyPI
34s
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:78e9ada6db919421069e76692b5aa5d8fd97b58b81b64d01911635bda98fce9f
coverage-3.13.0 Expired
3.25 KB
sha256:febbdcbe3a2da32139509c474be58865e10ed51d2d0c8c625260b40fad827f10