Skip to content

chore: Change blob ID calculation in forc-deploy to use configurables… #3421

chore: Change blob ID calculation in forc-deploy to use configurables…

chore: Change blob ID calculation in forc-deploy to use configurables… #3421

Triggered via push March 6, 2025 04:43
Status Success
Total duration 18m 50s
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/et/he/ethereum-types` (3.164.206.90), 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.90), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/gi/t2/git2` (3.164.206.90), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/ex/pe/expect-test` (3.164.206.90), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/2/im` (3.164.206.90), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/wa/lk/walkdir` (3.164.206.90), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/nu/mt/numtoa` (3.164.206.90), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/wi/t-/wit-bindgen-rt` (3.164.206.90), 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.90), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/un/ic/unicode-width` (3.164.206.90), 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/