Skip to content

fix(deps): update hibernate core to v7 (major) #2301

fix(deps): update hibernate core to v7 (major)

fix(deps): update hibernate core to v7 (major) #2301

Triggered via pull request February 8, 2026 01:49
Status Failure
Total duration 4m 35s
Artifacts 13

docker-build-test.yml

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

Annotations

12 errors and 12 warnings
build-test (docker-compose.yml, Dockerfile.graalvm-jvm.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.cockroachdb.yml, Dockerfile.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.hsqldb.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.hsqldb.yml, Dockerfile.azul.ci)
Process completed with exit code 1.
build-test (testing/docker-compose.hsqldb.yml, Dockerfile.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~5E192F.dockerbuild
19.4 KB
sha256:cf69306c2cc15b4ce79e4da9cb7797509800786d0326bced116764320ac603a7
TeamPiped~Piped-Backend~7BJ01Y.dockerbuild
18.6 KB
sha256:88b2b7729409feac50aa323eef7c1daf7930639a200c78135fdb3e752bc094c9
TeamPiped~Piped-Backend~D1TMX0.dockerbuild
19.2 KB
sha256:c8e070408fb92b64fea30b442bbadfc51995449be982ddc89230974a192a819b
TeamPiped~Piped-Backend~J91G7T.dockerbuild
25.6 KB
sha256:7c91e3ea73f2eb86a1b134d03dbc13c08f934de935468f789be4de1005e03724
TeamPiped~Piped-Backend~JNINAX.dockerbuild
18.1 KB
sha256:da198f720a4c93c63dad0865880d827993c22dba23a2f1db0153e2fd0869c803
TeamPiped~Piped-Backend~NWZ44N.dockerbuild
24.9 KB
sha256:5a5c4c7564b7b5a13ad4057acf72ecf5f33d7457c5ce005a28df9a3ca9f6239d
TeamPiped~Piped-Backend~NZT4IU.dockerbuild
25.2 KB
sha256:a1d2848464d37e4868d0d3e03c11d8f82de9d618b9417ca7882c2a5a36dd38ce
TeamPiped~Piped-Backend~O9Z900.dockerbuild
26.3 KB
sha256:75721716b8a5c7682a841e4d9ef84e621f2dc450302bdf33543c4e4693719347
TeamPiped~Piped-Backend~POICTY.dockerbuild
19.3 KB
sha256:a24666068a7d870ce4482cf6c30cdde322295fc672d82967265fe1e9044b6182
TeamPiped~Piped-Backend~Q1VLMN.dockerbuild
18.1 KB
sha256:ba2a6876d7669814af06f1642f00fd8dda8a6be276f2f5ff8d4b43ed8cde5fb7
TeamPiped~Piped-Backend~Q9W383.dockerbuild
19.6 KB
sha256:2d5a38b3a3558f75dbb8c22290d5b047a024480fefe85be138cfc8604a31a670
TeamPiped~Piped-Backend~UF22E0.dockerbuild
19.3 KB
sha256:10f71c1381efe0a2a9a9222b3880d825dbe19605825ade412c45e1272483b1c8
piped.jar
83 MB
sha256:a4487f1c92cdc0efde0f1edff629279bef8775460959b1cc31fe36578411c9c5