Skip to content

fix(deps): update react monorepo to v19.2.5 #3

fix(deps): update react monorepo to v19.2.5

fix(deps): update react monorepo to v19.2.5 #3

Triggered via pull request April 28, 2026 06:56
Status Failure
Total duration 2m 39s
Artifacts

test.yml

on: pull_request
Server Tests
2m 30s
Server Tests
Client Tests
1m 13s
Client Tests
Plugin Tests
24s
Plugin Tests
Electrobun Desktop Contract
1m 41s
Electrobun Desktop Contract
Cloud Live E2E (Eliza Cloud)
24s
Cloud Live E2E (Eliza Cloud)
All Tests Passed
3s
All Tests Passed
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 5 warnings
Cloud Live E2E (Eliza Cloud)
The process '/usr/bin/git' failed with exit code 128
Cloud Live E2E (Eliza Cloud)
Fetched in submodule path 'cloud', but it did not contain acceb080f45ef22bfe21ddb0e2c6091af5cc2fbd. Direct fetching of that commit failed.
Cloud Live E2E (Eliza Cloud)
remote error: upload-pack: not our ref acceb080f45ef22bfe21ddb0e2c6091af5cc2fbd
Plugin Tests
The process '/usr/bin/git' failed with exit code 128
Plugin Tests
Fetched in submodule path 'cloud', but it did not contain acceb080f45ef22bfe21ddb0e2c6091af5cc2fbd. Direct fetching of that commit failed.
Plugin Tests
remote error: upload-pack: not our ref acceb080f45ef22bfe21ddb0e2c6091af5cc2fbd
Client Tests
Process completed with exit code 128.
Electrobun Desktop Contract
Process completed with exit code 128.
Server Tests
Process completed with exit code 128.
All Tests Passed
Process completed with exit code 1.
Test gate
Required job 'cloud-live-e2e' finished with 'failure' (expected success)
Test gate
Required job 'desktop-contract' finished with 'failure' (expected success)
Test gate
Required job 'plugin-tests' finished with 'failure' (expected success)
Test gate
Required job 'client-tests' finished with 'failure' (expected success)
Test gate
Required job 'server-tests' finished with 'failure' (expected success)
Cloud Live E2E (Eliza Cloud)
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 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/
Plugin Tests
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 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/
Client Tests
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-node@v4, actions/setup-python@v5. 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/
Electrobun Desktop Contract
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-node@v4, actions/setup-python@v5. 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/
Server Tests
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-node@v4, actions/setup-python@v5. 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/