Skip to content

Publish

Publish #146

Triggered via release January 17, 2025 17:31
@willydouhardwillydouhard
published 0904f0f
Status Failure
Total duration 15m 14s
Artifacts

publish.yaml

on: release
Matrix: ci / e2e-tests / ci
Matrix: ci / pytest / pytest
ci  /  ...  /  lint-backend
1m 12s
ci / lint-backend / lint-backend
ci  /  ...  /  ci
1m 25s
ci / lint-ui / ci
Upload release to PyPI
1m 53s
Upload release to PyPI
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
ci / lint-backend / lint-backend
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ci / lint-ui / ci
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ci / pytest / pytest (3.11, 0.115)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ci / pytest / pytest (3.12, 0.115)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ci / pytest / pytest (3.9, 0.115)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ci / pytest / pytest (3.10, 0.115)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ci / e2e-tests / ci (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ci / Run CI
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):