chore: move dev dependencies to workspace (#6966) #3407
sdankelAnnotations
1 error and 19 warnings
|
deploy
Process completed with exit code 101.
|
|
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
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/
|
|
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.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/re/vm/revm-primitives` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/ru/in/ruint` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/nu/-a/nu-ansi-term` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/re/vm/revm` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/pa/ri/parity-scale-codec` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/pa/ri/parity-scale-codec-derive` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/un/ic/unicase` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/co/ns/console` (3.164.206.8), got 503
|
|
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/fu/tu/futures-executor` (3.164.206.8), got 503
|