Skip to content

Bump to 0.66.9 (#7011) #3431

Bump to 0.66.9 (#7011)

Bump to 0.66.9 (#7011) #3431

Triggered via push March 11, 2025 12:43
Status Success
Total duration 22m 49s
Artifacts

gh-pages.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

19 warnings
deploy
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/
deploy
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/
deploy
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/
deploy
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/
deploy
package `futures-util v0.3.25` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
the following packages contain code that will be rejected by a future version of Rust: buf_redux v0.8.4, multipart v0.18.0
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/si/ze/sized-chunks` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/en/um/enum-iterator` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/uu/id/uuid` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/se/cp/secp256k1-sys` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/rt/oo/rtoolbox` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/fu/nt/funty` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/tr/ac/tracing-log` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/et/h-/eth-keystore` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/ze/ro/zerovec` (3.164.206.38), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/te/xt/text-size` (3.164.206.38), got 503
deploy
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/
deploy
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/
deploy
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/