Skip to content

fix(deps): update hibernate core to v6.6.34.final #2259

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

fix(deps): update hibernate core to v6.6.34.final #2259

Triggered via pull request October 27, 2025 16:09
Status Failure
Total duration 4m 31s
Artifacts 13

docker-build-test.yml

on: pull_request
build-jdk  /  build-and-test
1m 7s
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.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 (testing/docker-compose.hsqldb.yml, Dockerfile.graalvm-jvm.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.cockroachdb.yml, Dockerfile.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.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.yugabytedb.yml, Dockerfile.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.
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/
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/
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/
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~CAJY4P.dockerbuild
25.2 KB
sha256:d42f2c939b12293b53ea15c87b69b6be219c08d3cbc6e3d332c6aab63ecefab7
TeamPiped~Piped-Backend~IF7HXO.dockerbuild
17.7 KB
sha256:d4d1b0ca2d92d3bfba304bd217df8969f9b332c2aaa2446227d69d0374be657f
TeamPiped~Piped-Backend~MASISX.dockerbuild
24.9 KB
sha256:7d8849a56c209911bc237b3c54fefb3d135e1fac7dd1bab81b5f40c5157d8656
TeamPiped~Piped-Backend~PD3ZGJ.dockerbuild
17.2 KB
sha256:32253dfc539d7a2006ce226b2f9b7a4a56cf030e427c6a8ae558cdfd026a7004
TeamPiped~Piped-Backend~PJGVNI.dockerbuild
17.4 KB
sha256:d022404f113b0b81366ab2d7e3cfb6c78769d86c340c30ff53be77aca53cba87
TeamPiped~Piped-Backend~QAOLAN.dockerbuild
18.3 KB
sha256:b3c6b88df8a87fbb164057ad469b3c32dd17feb83d22da5861485d440e7e955c
TeamPiped~Piped-Backend~TTSE6M.dockerbuild
18.6 KB
sha256:25b45954e6e4d8a317a95af944e00f03ce62fed2cc05bea28494810e4d29671d
TeamPiped~Piped-Backend~U3E123.dockerbuild
18.2 KB
sha256:e872ab15b1854aa3b2f54deb0ae298a58d39d2f55790cc9bc83bd404c5ee008a
TeamPiped~Piped-Backend~UP70KC.dockerbuild
19.3 KB
sha256:bd5565f3645c058be2ebbca36a958264bfc7ab81c85a619cc7b9fecb1ae6c166
TeamPiped~Piped-Backend~WSRJE0.dockerbuild
24 KB
sha256:419c66dda4e8c18a2d713d7ba545fb33775cd067198e2c337f460e204380100b
TeamPiped~Piped-Backend~ZGNMOU.dockerbuild
19.2 KB
sha256:ad8344059e91b6ca2d98fcef46d2c137f64c817f1c749714dccd9f77e7ea0977
TeamPiped~Piped-Backend~ZLVDK9.dockerbuild
24.9 KB
sha256:ef32627d155017136fdecabfe7fbade80e11ed01c4e97ccc712aaaa8b8155185
piped.jar
80.7 MB
sha256:af27f8ce876b419bd44c0494540aa696ba261d6f5a9df9dea3047fcd6a1fb8ba