Canceling since a higher priority waiting request for Test-refs/heads/gh-readonly-queue/main/pr-638-ebc705a1e7a8bc5973625c5d435fe568068fdc6b exists

The operation was canceled.

Canceling since a higher priority waiting request for Test-refs/heads/gh-readonly-queue/main/pr-638-ebc705a1e7a8bc5973625c5d435fe568068fdc6b exists

The operation was canceled.

Canceling since a higher priority waiting request for Test-refs/heads/gh-readonly-queue/main/pr-638-ebc705a1e7a8bc5973625c5d435fe568068fdc6b exists

Canceling since a higher priority waiting request for Test-refs/heads/gh-readonly-queue/main/pr-638-ebc705a1e7a8bc5973625c5d435fe568068fdc6b exists

The operation was canceled.

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026