Skip to content

MINOR:Add 4.2.1 to docker_scan workflow #29612

MINOR:Add 4.2.1 to docker_scan workflow

MINOR:Add 4.2.1 to docker_scan workflow #29612

Triggered via pull request May 28, 2026 15:11
Status Success
Total duration 21m 16s
Artifacts 19

ci.yml

on: pull_request
build  /  Configure Workflow
5s
build / Configure Workflow
build  /  Compile and Check (Merge Ref)
4m 52s
build / Compile and Check (Merge Ref)
build  /  Load Test Catalog
23s
build / Load Test Catalog
Matrix: build / test
build  /  Collate Test Catalog
11s
build / Collate Test Catalog
build  /  CI checks completed
2s
build / CI checks completed
build  /  Update Test Catalog
0s
build / Update Test Catalog
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
build / Load Test Catalog
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / Compile and Check (Merge Ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / JUnit tests Java 25 (flaky)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / JUnit tests Java 17 (flaky)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / JUnit tests Java 17 (new)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / JUnit tests Java 25 (new)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / JUnit tests Java 17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / JUnit tests Java 25
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / Collate Test Catalog
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
build-scan-17-flaky-nonew
1.33 MB
sha256:e2a36e59c47dff76bd5d06b532b0a7c77c76b43f7b3d4e60cde867d708f9b2ef
build-scan-17-noflaky-new
1.38 MB
sha256:aee0c7d7fa2823bad2c70837c47883d2104bf03992de86d4be7b79206c73f48b
build-scan-17-noflaky-nonew
1.43 MB
sha256:e52a69a82fd1c2ef7210fab7d720d225c9695eaddb22367380e810cf30845c7e
build-scan-25-flaky-nonew
1.33 MB
sha256:4e2620449104502f7c2ef4934cc15a929c3563326edab0f8f19bdcbb62bc3ad4
build-scan-25-noflaky-new
1.39 MB
sha256:01b744aeda440ccdfb851adc767a3c7e0fe178b15ede3839463297abd02f6c43
build-scan-25-noflaky-nonew
1.43 MB
sha256:740b9dee51eb4f1fdd27ab302783cd5be7d6fcf9b1dd444036810705d70c5da2
check-reports
4.68 MB
sha256:3309538cb6da3948eb2a43fb0223f725e2344f3cec39c5651e465cc9057e5f4a
combined-test-catalog
229 KB
sha256:de4b5b17f2c80d5704569c456fd15bbd6262a96df4b169d49bd516006c6e6744
junit-reports-17-flaky-nonew
866 KB
sha256:af77adfc38c04124c5ad4b452ce5adb1e3cdfcf3a972e3a46fc73555fac9a643
junit-reports-17-noflaky-new
565 KB
sha256:6f6a4cea78f755005e93c41a8084258938cb26fcb5d3dd78923b6ea45e69ef15
junit-reports-17-noflaky-nonew
86.1 MB
sha256:aac1d5875a32deda71d10f39fdb57db4029d84a8591f2ff7329620aadc8ccb4e
junit-reports-25-flaky-nonew
857 KB
sha256:36ff5973fdbedc01c9e48e6da6b168a378f1ef037938342a50bada4f40848f32
junit-reports-25-noflaky-new
567 KB
sha256:9e27069239554590e74583cd37781e429851fbaa2ed47a6fc9d376ddc8aef241
junit-reports-25-noflaky-nonew
88.2 MB
sha256:277281036d3b258a0b9e72bd9a620d693bfa0d35367e7aa7fd82970398003a59
junit-xml-17-noflaky-new
143 KB
sha256:afde3536c355575a364d121b7c796a48a317fe17d06e9d70ca2557145755774c
junit-xml-17-noflaky-nonew
378 KB
sha256:86c3949ab66e30a771a65dca97d6acda2900112d2e7405d3f8cf25c05e7103c9
junit-xml-25-noflaky-new
143 KB
sha256:02ce7021dffe2878ada2aaefffa64b16f01de841c0f01f37fc9f85f6e83aad39
junit-xml-25-noflaky-nonew
380 KB
sha256:f3732306253216199c54a8f8dc0a229e873007dd211729af096ecfb07b43dc46
test-catalog
10.7 KB
sha256:aed15684d425cfd3e72b12b8f4f63e62e0bb30126addf8e7fe8333a61703cdd6