Change Token fetching to refer to IsSupportedChain instead of GetSupportedChains #3851
test-deployments.yml
on: pull_request
detect_deployments_changes
7s
test-evm-deployments
1m 15s
test-solana-deployments
test-deployments
test-deployments-crosschain
1m 14s
Annotations
5 errors and 5 warnings
|
test-deployments-crosschain
Canceling since a higher priority waiting request for deployments-refs/pull/1837/merge exists
|
|
test-deployments-crosschain
The operation was canceled.
|
|
test-evm-deployments
Canceling since a higher priority waiting request for deployments-refs/pull/1837/merge exists
|
|
test-evm-deployments
The operation was canceled.
|
|
Test Deployments
Canceling since a higher priority waiting request for deployments-refs/pull/1837/merge exists
|
|
detect_deployments_changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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-deployments-crosschain
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-go@0c52d547c9bc32b1aa3301fd7a9cb496313a4491. 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-deployments-crosschain
Failed to restore: Cache service responded with 400
|
|
test-evm-deployments
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-go@0c52d547c9bc32b1aa3301fd7a9cb496313a4491. 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-evm-deployments
Failed to restore: Cache service responded with 400
|