Skip to content

chore(deps-dev): Bump eslint from 8.57.1 to 9.15.0 #2777

chore(deps-dev): Bump eslint from 8.57.1 to 9.15.0

chore(deps-dev): Bump eslint from 8.57.1 to 9.15.0 #2777

Triggered via push November 18, 2024 07:58
Status Failure
Total duration 7m 2s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
3m 18s
Lint / Broken Markdown links
Lint  /  Super Linter
6m 50s
Lint / Super Linter
Build & Test  /  Build Node.js
3m 4s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
6m 8s
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.
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/
Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L81
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "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#L95
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#L137
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#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#L106
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "EXTERNAL_DB_ENCRYPTION_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#L123
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#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/
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/
Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L91
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "STRIPE_WEBHOOK_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size
cheqd~studio~MANZY9.dockerbuild
60.5 KB
studio-staging
706 MB