Skip to content
Build and push image to registry

build(deps-dev): bump lodash from 4.17.21 to 4.17.23 (#1179) #1215

Sign in to view logs

build(deps-dev): bump lodash from 4.17.21 to 4.17.23 (#1179)

build(deps-dev): bump lodash from 4.17.21 to 4.17.23 (#1179) #1215

Triggered via push February 16, 2026 15:19
@andreiioandreiio
pushed 38ebdba
main
Status Success
Total duration 2m 44s
Artifacts 1

build-image.yml

on: push
build  /  Build and push image to registry
2m 40s
build / Build and push image to registry
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L82
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#L62
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#L61
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#L60
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
code4romania~website-factory~NKLVZR.dockerbuild Expired
118 KB
sha256:4609f7bf77fc43a6ce50e85c0500fc34abe7c2697c39d42b89dc25a3b77c2ff7