Skip to content

fix: Switch upgrade name given precedence (#840) #4305

fix: Switch upgrade name given precedence (#840)

fix: Switch upgrade name given precedence (#840) #4305

Triggered via push January 15, 2025 11:45
Status Success
Total duration 26m 58s
Artifacts 10

dispatch.yml

on: push
Build  /  Docker image
18s
Build / Docker image
Release  /  Super Linter
Release / Super Linter
Release  /  Check release condition
Release / Check release condition
Release  /  Docker image
Release / Docker image
Release  /  Node binary
Release / Node binary
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Build / Node binary
You are using 'latest' as default version. Will lock to '~> v2'.
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L8
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
cheqd-node-build.tar Expired
54.9 MB
cheqd-noded Expired
28.1 MB
cheqd~cheqd-node~ZDUTWR.dockerbuild Expired
25.7 KB
report-integration.xml Expired
8.66 KB
report-post-upgrade.xml Expired
1.85 KB
report-pre-upgrade.xml Expired
2.99 KB
report-pricing-change.xml Expired
7.15 KB
report-pricing-proposal.xml Expired
2.29 KB
report-unit.xml Expired
18.5 KB
report-upgraded-integration.xml Expired
8.58 KB