The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

package `futures-util v0.3.25` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

the following packages contain code that will be rejected by a future version of Rust: buf_redux v0.8.4, multipart v0.18.0

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/fu/tu/futures-executor` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/po/st/postcard` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/me/mo/memoffset` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/re/do/redox_syscall` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/sh/el/shell-words` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/fu/el/fuel-core-metrics` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/no/ti/notify` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/vc/pk/vcpkg` (18.245.46.85), got 503

spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/li/bd/libdbus-sys` (18.245.46.85), got 503