Skip to content
Build and publish container develop

ci: prevent catch-all from adding parent packages as wildcard extras #65

Sign in to view logs

ci: prevent catch-all from adding parent packages as wildcard extras

ci: prevent catch-all from adding parent packages as wildcard extras #65

Triggered via push April 16, 2026 05:28
@constantine2ndconstantine2nd
pushed 03efaad
develop
Status Success
Total duration 17m 27s
Artifacts 8

build_container.yml

on: push
compile
5m 20s
compile
Matrix: test
report
9s
report
docker
0s
docker
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
compile
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, 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/
test (3, v5_1 + v3_1 + http4sbridge + v7 + code.api + util + connector, code.api.v5_1_0 code.api....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, 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/
test (1, v4 + v5_0 + v3_0 + v2 + small, code.api.v4_0_0 code.api.v5_0_0 code.api.v3_0_0 code.api....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, 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/
test (2, v1_2_1 + v6 + ResourceDocs + util + berlin + small, code.api.v1_2_1 code.api.v6_0_0 code...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, 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/
report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-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
03efaad80818a971b0d83c4883876e9e0cdc0a79
264 MB
sha256:5acc8129960b9935ac7a73ef11fb8ed130302c99ae890edebbadd78fb7103d58
compiled-output Expired
351 MB
sha256:595cd87eefc73864fce149faa4641d540ae2aa98d7f4bc048e9334d0fef8348c
maven-build-log-shard1
241 KB
sha256:83e4248d9da3e5863e1eedd65b7d0be802e606fc50033ecb23230cbeadb740f3
maven-build-log-shard2
419 KB
sha256:f5bd7e6b984c44d5386e466fe7f0d590c063e111e49395e1a4160a2cd4909970
maven-build-log-shard3
199 KB
sha256:e299ac3085731538e6c16b4cbb9e728497ca79f669f29421c1316e5c3d264448
test-reports-shard1
1.85 MB
sha256:22711f9ea49214a18143df890b4ee683d4a330ca1fee9b2bb3e6c9b97b0040db
test-reports-shard2
1.31 MB
sha256:43df5c20368d0d7f4d26039d987f1e449a9af34a9c97580f1e13c8953e1eab3e
test-reports-shard3
1.49 MB
sha256:a36b83fac67d221739b615229c1f4878db08be38a37fd53a7392bdc9f6511b56