Skip to content
Create and publish a Docker image

Merge pull request #1470 from mkevenaar/renovate/lock-file-maintenance #1486

Sign in to view logs

Merge pull request #1470 from mkevenaar/renovate/lock-file-maintenance

Merge pull request #1470 from mkevenaar/renovate/lock-file-maintenance #1486

Triggered via push September 14, 2025 09:01
@mkevenaarmkevenaar
pushed 1adad04
develop
Status Success
Total duration 35s
Artifacts 1

docker-image.yaml

on: push
build-and-push-image
32s
build-and-push-image
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
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#L5
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: Dockerfile#L4
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TOKEN") 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: 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/

Artifacts

Produced during runtime
Name Size Digest
mkevenaar~CharlieSpring~YF5FLQ.dockerbuild
18.1 KB
sha256:242ce376a6ea7c73b5fdfd7ef01a26742da4a0159ca2979a3611d9d3af2c5ba6