Skip to content

Release Java Variant - release-26.04.28-03 #48

Release Java Variant - release-26.04.28-03

Release Java Variant - release-26.04.28-03 #48

Triggered via push May 8, 2026 19:43
Status Success
Total duration 1h 7m 48s
Artifacts –
Extract Version
2s
Extract Version
Initialize  /  Initialize
5s
Initialize / Initialize
Initialize  /  Check Previous Build
7s
Initialize / Check Previous Build
Initialize  /  Check Changed Files
3s
Initialize / Check Changed Files
Build  /  Initial Artifact Build
17m 21s
Build / Initial Artifact Build
Deployment  /  deployment
32m 7s
Deployment / deployment
Release  /  Release SBOM
0s
Release / Release SBOM
Release  /  Release Artifacts
13m 23s
Release / Release Artifacts
Release  /  ...  /  release-labeling
Release / Release Labeling / release-labeling
Finalize  /  Prepare Report Data
4s
Finalize / Prepare Report Data
Finalize  /  Final Status
4s
Finalize / Final Status
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build / Initial Artifact Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@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/
Deployment / deployment
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, docker/build-push-action@v6.15.0, docker/login-action@v3.0.0, docker/metadata-action@v5, docker/setup-buildx-action@v3.10.0, docker/setup-qemu-action@v3.6.0, slackapi/slack-github-action@v1.26.0. 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/
Release / Release Artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/download-artifact@v4, whelk-io/maven-settings-xml-action@v20. 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/
Finalize / Prepare Report Data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/