Skip to content

remove deprecated shardingsphere based sharding solution and examples #21

remove deprecated shardingsphere based sharding solution and examples

remove deprecated shardingsphere based sharding solution and examples #21

Triggered via pull request March 11, 2026 14:51
Status Success
Total duration 1m 4s
Artifacts 2

persistence-sharding-ci.yml

on: pull_request
Test Persistence Sharding
33s
Test Persistence Sharding
Build Persistence Sharding
22s
Build Persistence Sharding
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Test Persistence Sharding
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/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. 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 Persistence Sharding
No files were found with the provided path: persistence-sharding/target/site/jacoco/. No artifacts will be uploaded.
Test Persistence Sharding
No files were found with the provided path: persistence-sharding/target/surefire-reports/. No artifacts will be uploaded.
Build Persistence Sharding
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. 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
integration-test-results-sharding Expired
412 Bytes
sha256:f8041a8e642e0ada2254064c46785cc99af27ce7ab9059fedb1fa967036718f2
persistence-sharding-jar Expired
8.06 KB
sha256:c25309c243b62dcf70bd8dd511a8f456583d7235120196548c1c1e6f7e7d12e1