Skip to content
CI

Correct check for legacy file #74

Sign in to view logs

Correct check for legacy file

Correct check for legacy file #74

Triggered via push January 8, 2025 15:58
@stephenfinstephenfin
pushed 9b5f3ef
issues/74
Status Success
Total duration 1m 21s
Artifacts 1

ci.yaml

on: push
Matrix: Run unit tests
Run linters
47s
Run linters
Build docs
31s
Build docs
Upload release artifacts
34s
Upload release artifacts
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Run unit tests (3.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run unit tests (3.9)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run unit tests (3.11)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run unit tests (3.10)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run unit tests (3.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build docs
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run linters
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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
html-docs-build Expired
7.38 MB
sha256:ccd581a5e3d414e7f4ab173dfb41decce1101483c5758ff096542c60003c41c0