Skip to content

build(deps): bump the uv group across 1 directory with 2 updates #7

build(deps): bump the uv group across 1 directory with 2 updates

build(deps): bump the uv group across 1 directory with 2 updates #7

Triggered via pull request May 19, 2026 21:50
Status Failure
Total duration 1d 0h 0m 2s
Artifacts

publish-dry-runs.yml

on: pull_request
Python (wheel build)
5m 4s
Python (wheel build)
Compat check  /  compat-test
15s
Compat check / compat-test
Rust publish dry-run
46s
Rust publish dry-run
Matrix: check-java-publish-build
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 1 warning, and 2 notices
Compat check / compat-test
Process completed with exit code 127.
check-java-publish-build (aarch64-unknown-linux-gnu, runs-on=26127468501/runner=arm64-medium/imag...
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
check-java-publish-build (x86_64-unknown-linux-gnu, runs-on=26127468501/runner=amd64-medium/image...
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Python (wheel build)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/
sccache stats - compat-test
0% - 0 hits, 0 misses, 0 errors
sccache stats - rust-publish-dry-run
0% - 0 hits, 0 misses, 0 errors