2.0.602 #151
Triggered via release
January 27, 2025 12:28
willydouhard
willydouhard
published
2.0.602
Status
Success
Total duration
17m 15s
Artifacts
–
publish.yaml
on: release
Matrix: ci / e2e-tests / ci
Matrix: ci / pytest / pytest
ci
/
...
/
lint-backend
1m 24s
ci
/
...
/
ci
1m 40s
Upload release to PyPI
2m 53s
Annotations
13 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-backend / lint-backend
Unexpected input(s) 'version-file', valid inputs are ['args', 'src', 'version', 'changed-files']
|
|
ci / lint-backend / lint-backend
Unexpected input(s) 'version-file', valid inputs are ['args', 'src', 'version', 'changed-files']
|
|
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.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 / 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.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 / 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):
|