Back to pull request #585

chore(deps-dev): Bump tsx from 4.17.0 to 4.19.0 #2540

Sign in to view logs

Triggered via push September 2, 2024 07:34

dependabot[bot]

dependabot/npm_and_yarn/develop/tsx-4.19.0

Status Failure

Total duration 6m 57s

Artifacts 3

dispatch.yml

on: push

Lint / Broken Markdown links

Lint / Super Linter

Build & Test / Build Node.js

Build & Test / Build Docker image

Release / Semantic Release

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.

Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L81

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "VERIDA_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#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#L115

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#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/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L130

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#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#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/

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/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L100

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~RSLJ1K.dockerbuild Expired	59.9 KB
playwright-report Expired	194 Bytes
studio-staging Expired	707 MB