chore(deps-dev): Bump @types/node from 20.16.10 to 22.10.1 #2784
dispatch.yml
on: push
Lint
/
Broken Markdown links
2m 48s
Lint
/
Super Linter
6m 54s
Build & Test
/
Build Node.js
3m 3s
Build & Test
/
Build Docker image
6m 26s
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
|
Sensitive data should not be used in the ARG or ENV commands:
docker/Dockerfile#L82
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "POLYGON_PRIVATE_KEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
Variables should be defined before their use:
docker/Dockerfile#L101
UndefinedVar: Usage of undefined variable '$APPLICATION_BASE_URL'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
docker/Dockerfile#L101
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/
|
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#L127
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "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#L136
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/
|
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/
|
Sensitive data should not be used in the ARG or ENV commands:
docker/Dockerfile#L90
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "STRIPE_PUBLISHABLE_KEY")
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~33VANN.dockerbuild
Expired
|
60.1 KB |
|
studio-staging
Expired
|
751 MB |
|