Skip to content

Use WarpBuild runners for CI workflows (#600) #407

Use WarpBuild runners for CI workflows (#600)

Use WarpBuild runners for CI workflows (#600) #407

Triggered via push March 23, 2026 08:24
Status Success
Total duration 12m 26s
Artifacts

push-release.yml

on: push
publish-to-maven-central  /  Publish
12m 22s
publish-to-maven-central / Publish
Fit to window
Zoom out
Zoom in

Annotations

1 warning
publish-to-maven-central / Publish
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@v3, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/