Skip to content

Bump pydantic-core from 2.28.0 to 2.30.0 #322

Bump pydantic-core from 2.28.0 to 2.30.0

Bump pydantic-core from 2.28.0 to 2.30.0 #322

Triggered via pull request February 26, 2025 08:54
Status Failure
Total duration 30m 41s
Artifacts 2

test-pr.yaml

on: pull_request_target
fail_on_remote
0s
fail_on_remote
publish_artifacts  /  Build and push images
2m 27s
publish_artifacts / Build and push images
publish_artifacts  /  Build and push Helm chart
28s
publish_artifacts / Build and push Helm chart
run_azimuth_tests
27m 9s
run_azimuth_tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 13 warnings
run_azimuth_tests
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: Dockerfile#L64
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#L66
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#L40
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#L57
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#L61
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#L39
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#L41
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#L42
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#L65
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']
run_azimuth_tests
No files were found with the provided path: output.xml log.html report.html. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size
azimuth-cloud~cluster-api-addon-provider~X3HCPG.dockerbuild
75.6 KB
debug-bundle
17.3 KB