Skip to content

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

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

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

Triggered via push November 2, 2024 15:10
Status Success
Total duration 6m 13s
Artifacts 5

deploy.yml

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

Annotations

35 warnings
Legacy key/value format with whitespace separator should not be used: docker-images/python3.10.dockerfile#L35
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#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/
Legacy key/value format with whitespace separator should not be used: docker-images/python3.10.dockerfile#L43
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#L47
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#L52
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#L32
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.
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#L52
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#L32
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#L35
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#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/
Legacy key/value format with whitespace separator should not be used: docker-images/python3.9.dockerfile#L43
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#L47
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#L35
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#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/
Legacy key/value format with whitespace separator should not be used: docker-images/python3.11.dockerfile#L43
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#L47
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#L52
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#L32
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#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/
Legacy key/value format with whitespace separator should not be used: docker-images/python3.12.dockerfile#L43
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#L47
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#L52
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#L32
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#L35
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#L32
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#L35
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#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/
Legacy key/value format with whitespace separator should not be used: docker-images/python3.12.dockerfile#L43
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#L47
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#L52
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.

Artifacts

Produced during runtime
Name Size
tiangolo~uwsgi-nginx-docker~AWN7OX.dockerbuild
138 KB
tiangolo~uwsgi-nginx-docker~HCDYUK.dockerbuild
135 KB
tiangolo~uwsgi-nginx-docker~P1OW1Y.dockerbuild
136 KB
tiangolo~uwsgi-nginx-docker~PC4GPU.dockerbuild
135 KB
tiangolo~uwsgi-nginx-docker~YZG1CK.dockerbuild
138 KB