Skip to content
CI

Update build workflow (#12) #32

Sign in to view logs

Update build workflow (#12)

Update build workflow (#12) #32

Triggered via push January 10, 2025 06:19
@btschwertfegerbtschwertfeger
pushed 4285933
master
Status Success
Total duration 1m 21s
Artifacts 1

ci.yaml

on: push
Pre-Commit  /  Pre-Commit
17s
Pre-Commit / Pre-Commit
Matrix: CodeQL / Analyze
Matrix: Build
Upload current development version to Test PyPI  /  Publish Python distribution to PyPI
12s
Upload current development version to Test PyPI / Publish Python distribution to PyPI
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Pre-Commit / Pre-Commit
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build (ubuntu-latest, 3.11) / Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build (ubuntu-latest, 3.11) / Build
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Build (ubuntu-latest, 3.13) / Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build (ubuntu-latest, 3.13) / Build
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
CodeQL / Analyze (python)
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
python-package-distributions Expired
253 KB