Skip to content

chore(deps): Bump helmet from 7.2.0 to 8.0.0 #2773

chore(deps): Bump helmet from 7.2.0 to 8.0.0

chore(deps): Bump helmet from 7.2.0 to 8.0.0 #2773

Triggered via push November 8, 2024 06:00
Status Failure
Total duration 7m 10s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
3m 1s
Lint / Broken Markdown links
Lint  /  Super Linter
6m 59s
Lint / Super Linter
Build & Test  /  Build Node.js
3m 8s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
6m 27s
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#L98
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#L117
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#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#L119
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#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/
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#L124
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#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#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~11TQ32.dockerbuild
60.1 KB
studio-staging
706 MB