Skip to content
Build and push image to registry

build(deps-dev): bump tailwindcss from 3.4.7 to 3.4.10 (#836) #907

Sign in to view logs

build(deps-dev): bump tailwindcss from 3.4.7 to 3.4.10 (#836)

build(deps-dev): bump tailwindcss from 3.4.7 to 3.4.10 (#836) #907

Triggered via push September 20, 2024 22:51
@andreiioandreiio
pushed 6364919
main
Status Success
Total duration 2m 8s
Artifacts 1

build-image.yml

on: push
build  /  Build and push image to registry
1m 59s
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#L59
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/
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#L81
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
code4romania~website-factory~LNG0HG.dockerbuild
43.2 KB