Skip to content
Build Docker Image

Merge pull request #135 from walnuts1018/renovate/node-22.x-lockfile #385

Sign in to view logs

Merge pull request #135 from walnuts1018/renovate/node-22.x-lockfile

Merge pull request #135 from walnuts1018/renovate/node-22.x-lockfile #385

Triggered via push February 2, 2025 03:37
@walnuts1018walnuts1018
pushed cbf28a9
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~SQHQK7.dockerbuild
65.3 KB