Skip to content

chore(deps-dev): Bump @types/node from 20.16.10 to 22.10.1 #2781

chore(deps-dev): Bump @types/node from 20.16.10 to 22.10.1

chore(deps-dev): Bump @types/node from 20.16.10 to 22.10.1 #2781

Triggered via push December 2, 2024 07:51
Status Failure
Total duration 7m 13s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
3m 44s
Lint / Broken Markdown links
Lint  /  Super Linter
7m 1s
Lint / Super Linter
Build & Test  /  Build Node.js
3m 5s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
6m 7s
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.
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L141
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/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L142
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#L105
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#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#L111
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#L143
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "STRIPE_WEBHOOK_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#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/

Artifacts

Produced during runtime
Name Size
cheqd~studio~G28J21.dockerbuild Expired
61.2 KB
studio-staging Expired
707 MB