Skip to content

fix: resolve schema mismatch in dataset.update() for datasets with js… #5

fix: resolve schema mismatch in dataset.update() for datasets with js…

fix: resolve schema mismatch in dataset.update() for datasets with js… #5

Triggered via push March 31, 2026 13:17
Status Cancelled
Total duration 1d 0h 0m 2s
Artifacts

java.yml

on: push
Rust Clippy and Fmt Check
4m 4s
Rust Clippy and Fmt Check
Matrix: build-and-test-java
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Build and Test with Java 11
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build and Test with Java 17
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build and Test with Java 21
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Rust Clippy and Fmt Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. 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/