Skip to content

Bump pydantic-core from 2.28.0 to 2.29.0 #348

Bump pydantic-core from 2.28.0 to 2.29.0

Bump pydantic-core from 2.28.0 to 2.29.0 #348

Triggered via pull request February 10, 2025 14:04
Status Success
Total duration 27m 46s
Artifacts 3

test-pr.yaml

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

Annotations

12 warnings
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#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#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#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#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#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: 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#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/
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']

Artifacts

Produced during runtime
Name Size
azimuth-cloud~azimuth-identity-operator~XT2CI2.dockerbuild
80.1 KB
debug-bundle
29.9 KB
test-report
224 KB