Skip to content

chore(deps): bump cc from 1.2.57 to 1.2.58 #3746

chore(deps): bump cc from 1.2.57 to 1.2.58

chore(deps): bump cc from 1.2.57 to 1.2.58 #3746

Triggered via pull request March 30, 2026 03:08
Status Failure
Total duration 21m 15s
Artifacts 4

ValidatePullRequest.yml

on: pull_request
docs-pr
5s
docs-pr
update-guest-locks  /  update-guest-locks
45s
update-guest-locks / update-guest-locks
spell check with typos
7s
spell check with typos
check license headers
6s
check license headers
Matrix: build-guests
code-checks  /  linux-checks
11m 43s
code-checks / linux-checks
code-checks  /  windows-checks
9m 24s
code-checks / windows-checks
Matrix: build-test
Waiting for pending jobs
Matrix: fuzzing / fuzz
Waiting for pending jobs
Matrix: run-examples
Waiting for pending jobs
report-ci-status
2s
report-ci-status
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
build-guests (release) / build-guests
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
report-ci-status
Process completed with exit code 1.
update-guest-locks / update-guest-locks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
build-guests (debug) / build-guests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
code-checks / windows-checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
code-checks / linux-checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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
c-guests-debug Expired
2.05 MB
sha256:b519cbfcf12f55b67054dd22c511d44496911db64efb6e1c1f34697ec6ad6013
interface-wasm Expired
1.19 KB
sha256:a055af7170c10fc073d1b82f1f95e62a5ddf907c53cac2841257417b67489072
rust-guests-debug Expired
3.13 MB
sha256:1f368f7042ad5b93fbcdaf2d02aa06d256bbbec4e99f3098ca2510d323867177
twoworlds-wasm Expired
363 Bytes
sha256:121412460c2eeb406ac2fd2c25327024db334f9daa9d5f99cbd6ae3a8a9da79e