Skip to content
CI/CD

kraken.spot.trade.create_order: stp_type should be stptype (#373) #784

Sign in to view logs

kraken.spot.trade.create_order: stp_type should be stptype (#373)

kraken.spot.trade.create_order: stp_type should be stptype (#373) #784

Triggered via push April 11, 2025 05:30
@btschwertfegerbtschwertfeger
pushed d79af96
master
Status Success
Total duration 23m 40s
Artifacts 2

cicd.yaml

on: push
Pre-Commit  /  Pre-Commit
27s
Pre-Commit / Pre-Commit
Matrix: CodeQL / Analyze
Matrix: Build
Build-Doc  /  Build
46s
Build-Doc / Build
Matrix: Test-Futures-Private
Matrix: Test-Futures-Public
Matrix: Test-Spot-Private
Matrix: Test-Spot-Public
CodeCov  /  Coverage
8m 18s
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
22s
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 Digest
coverage Expired
5.65 KB
sha256:ae57599de84fca9e72c16a294e2aa064167bf1cfc0ed5fe216b09e5171b2ecd1
python-package-distributions Expired
188 KB
sha256:4e75eb6ee80ea7b72f8103529b36f1119c6e2b7a841e7c8afb90d40fc67e210c