Skip to content

chore(deps-dev): Bump @typescript-eslint/parser from 8.6.0 to 8.12.2 #814

chore(deps-dev): Bump @typescript-eslint/parser from 8.6.0 to 8.12.2

chore(deps-dev): Bump @typescript-eslint/parser from 8.6.0 to 8.12.2 #814

Status Success
Total duration 1m 35s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
15s
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
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 (45.8s)

Artifacts

Produced during runtime
Name Size
cheqd~did-registrar~W1WOCO.dockerbuild
40.3 KB
did-registrar-staging
87.5 MB