Skip to content

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

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

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

Triggered via pull request March 6, 2026 07:32
Status Success
Total duration 36s
Artifacts 1

ci.yml

on: pull_request
Build  /  timestamp
2s
Build / timestamp
Build  /  exploit-db-server
28s
Build / exploit-db-server
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build / timestamp
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L92
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#L91
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#L89
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#L94
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
openclarity~exploit-db-server~75Y5HS.dockerbuild
63.8 KB
sha256:bfd991c2fc0cba5baae661aecbce1ef38de95d6f89984a058f61fc82f91af4fa