Skip to content
Release Java Binding

ci: drop skipStagingRepositoryClose for smoother staging #150

Sign in to view logs

ci: drop skipStagingRepositoryClose for smoother staging

ci: drop skipStagingRepositoryClose for smoother staging #150

Triggered via pull request April 27, 2026 15:19
@tisonkuntisonkun
opened #7436
drop-skipStagingRepositoryClose
Status Success
Total duration 29m 59s
Artifacts 5

release_java.yml

on: pull_request
Matrix: stage-snapshot
deploy-staged-snapshots
21s
deploy-staged-snapshots
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
stage-snapshot (ubuntu-24.04-arm, linux-aarch_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
stage-snapshot (macos-latest, osx-aarch_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
stage-snapshot (macos-latest, osx-x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
stage-snapshot (windows-latest, windows-x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
stage-snapshot (ubuntu-latest, linux-x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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
linux-aarch_64-local-staging
24.6 MB
sha256:2e828bfb281d7daf986c34386cdcd2af4ab2dda261f7e50a7adb9f92a016aead
linux-x86_64-local-staging
25.5 MB
sha256:ca6d8635a22ec223215c639a1b69c3ad20121de0907f7fff3a033e091cb2abe8
osx-aarch_64-local-staging
27.1 MB
sha256:28894447277acdbbdbad1bb968ef7a4ae813a75f506a1792acd907f515253eee
osx-x86_64-local-staging
27.7 MB
sha256:aefd450d3c9383b0247789dedb66af44db69bbfc3175e3428f97acbef2d53aa7
windows-x86_64-local-staging
25.1 MB
sha256:c9318099ef8f3b11571231bd9935ed346dcd52bb07ebfc785124712c84fa88ed