Skip to content

fix(deps): update hibernate core to v6.6.44.final #2283

fix(deps): update hibernate core to v6.6.44.final

fix(deps): update hibernate core to v6.6.44.final #2283

Triggered via pull request December 14, 2025 04:38
Status Failure
Total duration 4m 46s
Artifacts 13

docker-build-test.yml

on: pull_request
build-jdk  /  build-and-test
1m 1s
build-jdk / build-and-test
Matrix: build-test
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 12 warnings
build-test (testing/docker-compose.hsqldb.yml, Dockerfile.ci)
Process completed with exit code 1.
build-test (docker-compose.yml, Dockerfile.azul.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.hsqldb.yml, Dockerfile.azul.ci)
Process completed with exit code 1.
build-test (docker-compose.yml, Dockerfile.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.cockroachdb.yml, Dockerfile.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.hsqldb.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
build-test (docker-compose.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.cockroachdb.yml, Dockerfile.azul.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.cockroachdb.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.yugabytedb.yml, Dockerfile.azul.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.yugabytedb.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.yugabytedb.yml, Dockerfile.ci)
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: Dockerfile.graalvm-jvm.ci#L22
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.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile.graalvm-jvm.ci#L36
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile.graalvm-jvm.ci#L36
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Legacy key/value format with whitespace separator should not be used: Dockerfile.graalvm-jvm.ci#L22
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.graalvm-jvm.ci#L22
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.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile.graalvm-jvm.ci#L36
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile.graalvm-jvm.ci#L36
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Legacy key/value format with whitespace separator should not be used: Dockerfile.graalvm-jvm.ci#L22
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.graalvm-jvm.ci#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Artifacts

Produced during runtime
Name Size Digest
TeamPiped~Piped-Backend~2O8NPQ.dockerbuild
18.2 KB
sha256:51a582abe17c8c4cdf5c12367501816497009ddebf27f7a421ab0d70f4518491
TeamPiped~Piped-Backend~54PHUD.dockerbuild
18.5 KB
sha256:b71613a4ad5a6f4ae696fde28754d93d841dd7479ae77bc474614a051333f3f8
TeamPiped~Piped-Backend~64J2DF.dockerbuild
18.1 KB
sha256:1f5429df2123aca6e51242cc47faccf135b32625b3fc2fef5792f3af95a229d0
TeamPiped~Piped-Backend~EFA6F2.dockerbuild
24.9 KB
sha256:e188ad96818d144f7f6c5a5c9895367d4d417118021ad5185776fccd9eed9802
TeamPiped~Piped-Backend~I4FCTQ.dockerbuild
18.4 KB
sha256:6a76a179956e745598b3617a6c51433a0403be4f54547d85d9c532732fd04d79
TeamPiped~Piped-Backend~KOYHTJ.dockerbuild
19.7 KB
sha256:14fe91d5eae3926e69f4c2411f7d6c323e5887cff673df156e677b307b28e336
TeamPiped~Piped-Backend~LOBPS9.dockerbuild
24.9 KB
sha256:d2ca94b32e54d4ac44c00232948f66f8829370cc1185cb55627bc38aefe6086c
TeamPiped~Piped-Backend~OYJT1Y.dockerbuild
19.6 KB
sha256:7d79e8c5caf7c94bec193e08fc37b81f624f6aecf9cf2900a03b3061be92737a
TeamPiped~Piped-Backend~P6C7X5.dockerbuild
25.2 KB
sha256:0ff8f4d1eb3ee2356e5f41df103a4ddd813dc4fedd506930f9eb85018d369277
TeamPiped~Piped-Backend~SA9AAI.dockerbuild
18.3 KB
sha256:b3470b431e065657f78660236cd341f2942482a163f69c88bae13e699a311ed5
TeamPiped~Piped-Backend~SY3K3M.dockerbuild
17.8 KB
sha256:1dc00ea1cf556f7fd0a0160530acac9177123254dc910fe6bf189c954a97481d
TeamPiped~Piped-Backend~U4BMWI.dockerbuild
25.3 KB
sha256:ddb19889af04f08619ec549e4f2f04ca75f6e58e326ce82d48f06f7fc0300d9c
piped.jar
80.7 MB
sha256:4172d475609f767fa49f4fa2cae93fca7e8ca83bb25ce5723ee35e1904dc12a9