CI/CD

Resolve "Running GitHub Actions on contributions is cumbersome" (#400) #869

Sign in to view logs

Triggered via push September 21, 2025 06:06

master

Status Success

Total duration 21m 31s

Artifacts 2

cicd.yaml

on: push

Matrix: CodeQL / Analyze

Pre-Commit / Pre-Commit

Matrix: Build

Build-Doc / Build

Matrix: Test-Futures-Private

Matrix: Test-Spot-Private

Matrix: Test-Futures-Public

Matrix: Test-Spot-Public

CodeCov / Coverage

Upload release to PyPI / Publish Python distribution to PyPI

Upload development version to Test PyPI / Publish Python distribution to PyPI

Annotations

3 warnings and 14 notices

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.

Build (windows-latest, 3.12) / Build

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Build (windows-latest, 3.13) / Build

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Build (windows-latest, 3.11) / Build

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Futures-Public (windows-latest, 3.12) / Test windows-latest 3.12

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Futures-Public (windows-latest, 3.13) / Test windows-latest 3.13

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Futures-Public (windows-latest, 3.11) / Test windows-latest 3.11

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Spot-Public (windows-latest, 3.11) / Test windows-latest 3.11

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Spot-Public (windows-latest, 3.12) / Test windows-latest 3.12

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Spot-Public (windows-latest, 3.13) / Test windows-latest 3.13

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Futures-Private (windows-latest, 3.11) / Test windows-latest 3.11

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Spot-Private (windows-latest, 3.11) / Test windows-latest 3.11

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Futures-Private (windows-latest, 3.12) / Test windows-latest 3.12

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Futures-Private (windows-latest, 3.13) / Test windows-latest 3.13

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Test-Spot-Private (windows-latest, 3.13) / Test windows-latest 3.13

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Artifacts

Produced during runtime

Name	Size	Digest
coverage Expired	5.68 KB	`sha256:d1c6abc9d7069e09f18778ad7f4936bb02e3ec873aca3f724eac62b2b84e6a62`
python-package-distributions Expired	197 KB	`sha256:35a76684e9603b858e0f4e53ea3c1b1cf03c18e2b6048260b3c3d53ae0c1f807`