Skip to content

Merge pull request #106 from lsst/tickets/DM-48788 #820

Merge pull request #106 from lsst/tickets/DM-48788

Merge pull request #106 from lsst/tickets/DM-48788 #820

Triggered via push March 6, 2025 09:43
Status Failure
Total duration 1m 42s
Artifacts

build.yaml

on: push
Matrix: build_and_test
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
build_and_test (3.11)
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.11.11-pip-13394ddbc421592712f2ad94de3c21d6608897dd478514be9f58667789f1fd1c, setup-python-Linux-x64-24.04-Ubuntu-python-3.11.11-pip
build_and_test (3.12)
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.12.9-pip-13394ddbc421592712f2ad94de3c21d6608897dd478514be9f58667789f1fd1c, setup-python-Linux-x64-24.04-Ubuntu-python-3.12.9-pip
build_and_test (3.13)
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.13.2-pip-13394ddbc421592712f2ad94de3c21d6608897dd478514be9f58667789f1fd1c, setup-python-Linux-x64-24.04-Ubuntu-python-3.13.2-pip
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):