Bump anyio from 4.7.0 to 4.8.0 #340
Triggered via pull request
January 23, 2025 15:39
dependabot[bot]
synchronize
#254
Status
Success
Total duration
25m 28s
Artifacts
3
test-pr.yaml
on: pull_request_target
Annotations
15 warnings
fail_on_remote
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L74
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#L75
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#L49
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#L51
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#L71
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#L67
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#L76
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#L1
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#L50
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#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/
|
publish_artifacts / Build and push images
Unexpected input(s) 'github-token', valid inputs are ['checkout-path', 'cache-key', 'build-args', 'context', 'file', 'labels', 'platforms', 'pull', 'push', 'tags']
|
publish_artifacts / Build and push images
Unexpected input(s) 'github-token', valid inputs are ['checkout-path', 'cache-key', 'build-args', 'context', 'file', 'labels', 'platforms', 'pull', 'push', 'tags']
|
publish_artifacts / Build and push Helm chart
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
run_azimuth_tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
azimuth-cloud~azimuth-identity-operator~R6FZIN.dockerbuild
|
80.5 KB |
|
debug-bundle
|
30.1 KB |
|
test-report
|
224 KB |
|