chore(deps-dev): Bump eslint from 8.57.1 to 9.14.0 #2767
dispatch.yml
on: push
Lint
/
Broken Markdown links
2m 35s
Lint
/
Super Linter
7m 3s
Build & Test
/
Build Node.js
3m 5s
Build & Test
/
Build Docker image
6m 16s
Staging
/
Staging Deploy
Release
/
Release Docker image
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#L120
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#L135
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#L142
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "STRIPE_PUBLISHABLE_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#L116
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/
|
Legacy key/value format with whitespace separator should not be used:
docker/Dockerfile#L138
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#L55
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "EXTERNAL_DB_ENCRYPTION_KEY")
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#L65
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "COOKIE_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#L67
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "LOGTO_M2M_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#L94
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~LHZKC4.dockerbuild
Expired
|
61.2 KB |
|
studio-staging
Expired
|
706 MB |
|