Skip to content

Merge pull request #200 from piny940/renovate/eslint-config-prettier-… #149

Merge pull request #200 from piny940/renovate/eslint-config-prettier-…

Merge pull request #200 from piny940/renovate/eslint-config-prettier-… #149

Triggered via push January 14, 2025 03:22
Status Success
Total duration 3m 7s
Artifacts 2

prd-deploy.yaml

on: push
prd-build-backend
1m 2s
prd-build-backend
build-doc
0s
build-doc
prd-build-frontend
2m 44s
prd-build-frontend
prd-build-example
0s
prd-build-example
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
filter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
prd-build-backend
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: frontend/Dockerfile#L10
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: frontend/Dockerfile#L11
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: frontend/Dockerfile#L31
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: frontend/Dockerfile#L38
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
piny940~auth~J0L6YN.dockerbuild
61.6 KB
piny940~auth~UGJQV4.dockerbuild
43.6 KB