Skip to content
Publish to PyPI

Fix kriging analysis bugs (#302) #42

Sign in to view logs

Fix kriging analysis bugs (#302)

Fix kriging analysis bugs (#302) #42

Triggered via push November 16, 2024 02:08
@brandynluccabrandynlucca
pushed db10cc2
main
Status Success
Total duration 2m 31s
Artifacts 1

pypi.yaml

on: push
Build echopop package
17s
Build echopop package
Test echopop package
1m 56s
Test echopop package
Push echopop to production pypi
0s
Push echopop to production pypi
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
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
releases
5.89 MB