Skip to content

Merge branch 'grarco/update-fee-specs' (#386) #924

Merge branch 'grarco/update-fee-specs' (#386)

Merge branch 'grarco/update-fee-specs' (#386) #924

Triggered via push September 12, 2024 10:16
Status Success
Total duration 1m 52s
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~OJT3JQ.dockerbuild
22.2 KB
anoma~namada-docs~YBWB35.dockerbuild
21.1 KB
anoma~namada-docs~ZDST6G.dockerbuild
23.1 KB