Skip to content

Merge branhc 'grarco/update-reprot-specs' (#387) #928

Merge branhc 'grarco/update-reprot-specs' (#387)

Merge branhc 'grarco/update-reprot-specs' (#387) #928

Triggered via push September 12, 2024 13:31
Status Success
Total duration 2m 3s
Artifacts 3

build-docs.yml

on: push
Matrix: checks
Matrix: cloudfront
Matrix: docker
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
checks (docs, docs)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
checks (community, community)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L20
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#L20
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#L20
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
anoma~namada-docs~0JQ6TJ.dockerbuild
20.7 KB
anoma~namada-docs~AX8OXF.dockerbuild
22.5 KB
anoma~namada-docs~SIMSHM.dockerbuild
23 KB