Skip to content

⬆ Bump tiangolo/issue-manager from 0.5.0 to 0.5.1 (#387) #245

⬆ Bump tiangolo/issue-manager from 0.5.0 to 0.5.1 (#387)

⬆ Bump tiangolo/issue-manager from 0.5.0 to 0.5.1 (#387) #245

Triggered via push November 2, 2024 15:28
Status Success
Total duration 8m 44s
Artifacts 5

deploy.yml

on: push
Matrix: deploy
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
Legacy key/value format with whitespace separator should not be used: docker-images/python3.10.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: docker-images/python3.10.dockerfile#L13
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: docker-images/python3.10.dockerfile#L17
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/
deploy (python3.10, 3.10)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.12.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: docker-images/python3.12.dockerfile#L13
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: docker-images/python3.12.dockerfile#L17
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/
deploy (latest, 3.12)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.11.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: docker-images/python3.11.dockerfile#L13
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: docker-images/python3.11.dockerfile#L17
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/
deploy (python3.11, 3.11)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
deploy (python3.12, 3.12)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.12.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: docker-images/python3.12.dockerfile#L13
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: docker-images/python3.12.dockerfile#L17
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/
deploy (python3.9, 3.9)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.9.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: docker-images/python3.9.dockerfile#L13
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: docker-images/python3.9.dockerfile#L17
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
tiangolo~uwsgi-nginx-flask-docker~1HXPN7.dockerbuild
130 KB
tiangolo~uwsgi-nginx-flask-docker~I72GDF.dockerbuild
130 KB
tiangolo~uwsgi-nginx-flask-docker~IRCIKJ.dockerbuild
132 KB
tiangolo~uwsgi-nginx-flask-docker~ON0UYN.dockerbuild
130 KB
tiangolo~uwsgi-nginx-flask-docker~PY2ZHH.dockerbuild
128 KB