Skip to content

Fixes argument errors not displayed. (#5909) #3382

Fixes argument errors not displayed. (#5909)

Fixes argument errors not displayed. (#5909) #3382

Triggered via push February 9, 2025 01:50
Status Success
Total duration 15m 55s
Artifacts

gh-pages.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

25 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 `fuel-core-storage v0.41.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `parity-scale-codec-derive v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `scc v2.2.5` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `fuel-core-storage v0.41.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `parity-scale-codec-derive v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `scc v2.2.5` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `fuel-core-storage v0.41.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `parity-scale-codec-derive v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `fuel-core-storage v0.41.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `parity-scale-codec-derive v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `scc v2.2.5` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
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
package `fuel-core-storage v0.41.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `parity-scale-codec-derive v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `scc v2.2.5` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked