Skip to content
Check if a Docker image can be built

Build(deps): bump docker/build-push-action from 6 to 7 #1619

Sign in to view logs

Build(deps): bump docker/build-push-action from 6 to 7

Build(deps): bump docker/build-push-action from 6 to 7 #1619

Triggered via pull request March 6, 2026 15:52
@dependabotdependabot[bot]
opened #1483
dependabot/github_actions/docker/build-push-action-7
Status Success
Total duration 1m 23s
Artifacts 1

dockerimage.yml

on: pull_request
build_docker_image
1m 18s
build_docker_image
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L55
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#L49
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#L37
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#L30
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
macbre~phantomas~WZ3GKZ.dockerbuild
26 KB
sha256:e26658fec6ed1d49564cdd1788ce78031951b4942a188ff7ac98651007c45b45