Workflow Dispatch

chore(deps): Bump express in the npm_and_yarn group across 1 directory #2797

Sign in to view logs

Triggered via push February 27, 2025 12:00

dependabot[bot]

dependabot/npm_and_yarn/npm_and_yarn-14ce3b24ba

Status Failure

Total duration 7m 17s

Artifacts 2

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 11 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.

Build & Test / Build Node.js

Cache not found for keys: node-cache-Linux-x64-npm-de84f79d54303e687915760aa48b9968add632db9eb74236dd4b6131ff99bfef

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

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

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

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

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~ZK3DVC.dockerbuild	56 KB
studio-staging	751 MB