Skip to content
Build Docker Image

chore(deps): update dependency @eslint/compat to v1.2.6 (#134) #383

Sign in to view logs

chore(deps): update dependency @eslint/compat to v1.2.6 (#134)

chore(deps): update dependency @eslint/compat to v1.2.6 (#134) #383

Triggered via push February 1, 2025 21:57
@renovaterenovate[bot]
pushed 7effeda
main
Status Success
Total duration 1m 53s
Artifacts 1

docker.yaml

on: push
Build Walnuts.dev Docker Image
1m 45s
Build Walnuts.dev Docker Image
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L4
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: Dockerfile#L6
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: Dockerfile#L19
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: Dockerfile#L21
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
walnuts1018~walnuts.dev~JVSJS8.dockerbuild
66.3 KB