chore(deps-dev): Bump eslint from 8.57.1 to 9.16.0 #2788
dispatch.yml
on: push
Lint
/
Broken Markdown links
2m 45s
Lint
/
Super Linter
7m 2s
Build & Test
/
Build Node.js
3m 7s
Build & Test
/
Build Docker image
6m 19s
Staging
/
Staging Deploy
Release
/
Release Docker image
Annotations
2 errors and 14 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.
|
Lint / Broken Markdown links
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build & Test / Build Node.js
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build & Test / Build Docker image
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
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#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#L121
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#L138
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "POLYGON_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#L98
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/
|
Sensitive data should not be used in the ARG or ENV commands:
docker/Dockerfile#L116
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "COOKIE_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#L117
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#L89
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "STRIPE_SECRET_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#L123
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "LOGTO_WEBHOOK_SECRET")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
Lint / Super Linter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
cheqd~studio~QS0E5D.dockerbuild
Expired
|
59.8 KB |
|
studio-staging
Expired
|
751 MB |
|