Skip to content

chore: extra btc staking validation on tx to psbt conversion (#659) #370

chore: extra btc staking validation on tx to psbt conversion (#659)

chore: extra btc staking validation on tx to psbt conversion (#659) #370

Triggered via push January 30, 2025 04:30
Status Success
Total duration 7m 42s
Artifacts 14

publish.yaml

on: push
Matrix: docker_build
Matrix: dockerhub_publish
Matrix: ecr_publish
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size
babylonlabs-io~simple-staking~NLM259.dockerbuild
41.9 KB
babylonlabs-io~simple-staking~O95RNN.dockerbuild
41.8 KB
babylonlabs-io~simple-staking~QFSWJX.dockerbuild
42.8 KB
babylonlabs-io~simple-staking~QLZVRA.dockerbuild
41.2 KB
babylonlabs-io~simple-staking~S58M7V.dockerbuild
42 KB
babylonlabs-io~simple-staking~SJ66J4.dockerbuild
41.8 KB
babylonlabs-io~simple-staking~T4Q9KS.dockerbuild
41.8 KB
simple-staking-devnet
90.6 MB
simple-staking-mainnet
90.6 MB
simple-staking-mainnet-private
90.6 MB
simple-staking-phase-2-devnet
90.6 MB
simple-staking-phase-2-testnet
90.6 MB
simple-staking-staging
90.7 MB
simple-staking-testnet
90.6 MB