Skip to content

Move to s3path 0.6.0 so we work on python 3.13! #1169

Move to s3path 0.6.0 so we work on python 3.13!

Move to s3path 0.6.0 so we work on python 3.13! #1169

Triggered via push January 2, 2025 03:56
Status Success
Total duration 5m 10s
Artifacts 2
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
docker
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L3
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L27
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#L28
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/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L3
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L27
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#L28
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
pypa~bandersnatch~5AA7EC.dockerbuild
150 KB
pypa~bandersnatch~O88S6M.dockerbuild
132 KB