Skip to content

chore(deps-dev): Bump @types/uuid from 9.0.8 to 10.0.0 #797

chore(deps-dev): Bump @types/uuid from 9.0.8 to 10.0.0

chore(deps-dev): Bump @types/uuid from 9.0.8 to 10.0.0 #797

Triggered via push September 23, 2024 12:20
Status Success
Total duration 1m 30s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
10s
Lint / Broken Markdown links
Lint  /  Super Linter
1m 19s
Lint / Super Linter
Build & Test  /  Build Node.js
1m 8s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
41s
Build & Test / Build Docker image
Release  /  Release Docker image
Release / Release Docker image
Fit to window
Zoom out
Zoom in

Annotations

5 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/
Slow Test: [Integration tests] › resource/resource-create.spec.ts#L1
[Integration tests] › resource/resource-create.spec.ts took 17.5s
🎭 Playwright Run Summary
18 passed (48.1s)

Artifacts

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