Skip to content

chore(deps-dev): Bump @semantic-release/release-notes-generator from … #796

chore(deps-dev): Bump @semantic-release/release-notes-generator from …

chore(deps-dev): Bump @semantic-release/release-notes-generator from … #796

Triggered via push September 23, 2024 12:16
Status Success
Total duration 2m 44s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
24s
Lint / Broken Markdown links
Lint  /  Super Linter
1m 23s
Lint / Super Linter
Build & Test  /  Build Node.js
1m 7s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
39s
Build & Test / Build Docker image
Release  /  Release Docker image
0s
Release / Release Docker image
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 1 notice
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/
🎭 Playwright Run Summary
18 passed (45.4s)

Artifacts

Produced during runtime
Name Size
cheqd~did-registrar~OU8TPI.dockerbuild Expired
33.4 KB
did-registrar-staging Expired
86.5 MB