Skip to content

chore(deps): Bump the npm_and_yarn group across 1 directory with 3 up… #2590

chore(deps): Bump the npm_and_yarn group across 1 directory with 3 up…

chore(deps): Bump the npm_and_yarn group across 1 directory with 3 up… #2590

Triggered via push September 17, 2024 05:35
Status Failure
Total duration 7m 3s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
3m 15s
Lint / Broken Markdown links
Lint  /  Super Linter
6m 50s
Lint / Super Linter
Build & Test  /  Build Node.js
2m 59s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
6m 33s
Build & Test / Build Docker image
Release  /  Release Docker image
Release / Release Docker image
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
Build & Test / Build Node.js
Error: Timed out waiting 60000ms from config.webServer.
Build & Test / Build Node.js
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L132
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: docker/Dockerfile#L104
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: docker/Dockerfile#L112
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: docker/Dockerfile#L143
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/
Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L76
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "API_KEY_EXPIRATION") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L100
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/
Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L137
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "VERIDA_PRIVATE_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L144
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/
Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L63
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "LOGTO_APP_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L107
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~studio~35WGOW.dockerbuild
57.6 KB
studio-staging
705 MB