Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: withgraphite/graphite-ci-action@ee395f3a78254c006d11339669c6cabddf196f72. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ast-grep/action@cf62e780f0c88301228978d593a7784427a097a6. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<ImportMapping>` in `external_request_to_esm_import_mapping` with `Vc<ImportMapping>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<ImportMapping>` in `external_request_to_cjs_import_mapping` with `Vc<ImportMapping>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<ImportMapping>` in `request_to_import_mapping` with `Vc<ImportMapping>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<ImportMapping>` in `export_value_to_import_mapping` with `Vc<ImportMapping>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<Box<dyn Source>>` in `resolve_extends_rooted_or_relative` with `Vc<Box<dyn Source>>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<Box<dyn Source>>` in `resolve_extends` with `Vc<Box<dyn Source>>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<Box<dyn OutputAsset>>` in `create_app_paths_manifest` with `Vc<Box<dyn OutputAsset>>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<Box<dyn Module>>` in `to_rsc_context` with `Vc<Box<dyn Module>>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<Box<dyn OutputAsset>>` in `get_wasm_paths_from_root` with `Vc<Box<dyn OutputAsset>>` instead.

Returning a `ResolvedVc` in a turbo task is not recommended. Consider replacing `ResolvedVc<Box<dyn OutputAsset>>` in `get_referenced_server_assets` with `Vc<Box<dyn OutputAsset>>` instead.