chore(deps): Bump @stablelib/ed25519 from 1.0.3 to 2.0.0 #2557
dispatch.yml
on: push
Lint
/
Broken Markdown links
2m 33s
Lint
/
Super Linter
6m 45s
Build & Test
/
Build Node.js
2m 11s
Build & Test
/
Build Docker image
5m 46s
Staging
/
Staging Deploy
Release
/
Release Docker image
Annotations
2 errors and 10 warnings
Build & Test / Build Node.js
Error: Process from config.webServer was not able to start. Exit code: 1
|
Build & Test / Build Node.js
Process completed with exit code 1.
|
Legacy key/value format with whitespace separator should not be used:
docker/Dockerfile#L122
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#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/
|
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/
|
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/
|
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#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#L141
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "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#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#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/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
cheqd~studio~U8M1OT.dockerbuild
Expired
|
55.7 KB |
|
studio-staging
Expired
|
723 MB |
|