Skip to content
CI/CD

Update egress rules for PyPI publish (#320) #651

Sign in to view logs

Update egress rules for PyPI publish (#320)

Update egress rules for PyPI publish (#320) #651

Re-run triggered November 26, 2024 07:49
@btschwertfegerbtschwertfeger
4f86908
master
Status Success
Total duration 19m 6s
Artifacts 2

cicd.yaml

on: push
Pre-Commit  /  Pre-Commit
27s
Pre-Commit / Pre-Commit
Matrix: CodeQL / Analyze
Matrix: Build
Matrix: Test-Spot-Private
Build-Doc  /  Build
54s
Build-Doc / Build
Matrix: Test-Futures-Private
Matrix: Test-Futures-Public
Matrix: Test-NFT-Public
Matrix: Test-Spot-Public
Matrix: Test-NFT-Private
CodeCov  /  Coverage
8m 51s
CodeCov / Coverage
Upload release to PyPI  /  Publish Python distribution to PyPI
Upload release to PyPI / Publish Python distribution to PyPI
Upload development version to Test PyPI  /  Publish Python distribution to PyPI
19s
Upload development version to Test PyPI / Publish Python distribution to 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
coverage Expired
5.98 KB