Skip to content
Workflow Dispatch

Merge branch 'develop' #799

Sign in to view logs

Merge branch 'develop'

Merge branch 'develop' #799

Triggered via push September 23, 2024 12:35
@ankurdotbankurdotb
pushed d8357c8
main
Status Success
Total duration 3m 36s
Artifacts 3

dispatch.yml

on: push
Lint  /  Broken Markdown links
12s
Lint / Broken Markdown links
Lint  /  Super Linter
1m 23s
Lint / Super Linter
Build & Test  /  Build Node.js
1m 8s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
1m 5s
Build & Test / Build Docker image
Release  /  Semantic Release
35s
Release / Semantic Release
Staging  /  Staging Deploy
Staging / Staging Deploy
Release  /  Release Docker image
1m 12s
Release / Release Docker image
https://did-registrar.cheqd.net/api-docs
Fit to window
Zoom out
Zoom in

Annotations

8 warnings and 1 notice
🎭 Playwright Run Summary
18 passed (44.0s)
Legacy key/value format with whitespace separator should not be used: Dockerfile#L50
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: Dockerfile#L51
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: Dockerfile#L54
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: Dockerfile#L55
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: Dockerfile#L50
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: Dockerfile#L51
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: Dockerfile#L54
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: Dockerfile#L55
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~did-registrar~KU2B7I.dockerbuild
32.9 KB
cheqd~did-registrar~X3DQ2X.dockerbuild
39.2 KB
did-registrar-staging
86.5 MB