Skip to content

chore(deps-dev): Bump @types/node from 20.16.1 to 22.5.5 #780

chore(deps-dev): Bump @types/node from 20.16.1 to 22.5.5

chore(deps-dev): Bump @types/node from 20.16.1 to 22.5.5 #780

Triggered via push September 16, 2024 11:12
Status Success
Total duration 1m 27s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
15s
Lint / Broken Markdown links
Lint  /  Super Linter
1m 19s
Lint / Super Linter
Build & Test  /  Build Node.js
1m 1s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
58s
Build & Test / Build Docker image
Release  /  Release Docker image
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 (42.2s)

Artifacts

Produced during runtime
Name Size
cheqd~did-registrar~MQEMFU.dockerbuild Expired
38.9 KB
did-registrar-staging Expired
86.9 MB