chore(bench): Update criterion to 0.5 #1163
matheus23checks.yaml
on: pull_request
Matrix: rust-checks
Matrix: rust-tests
Matrix: wasm-js-tests
Annotations
12 errors and 20 warnings
|
wasm-js-tests (nightly)
Process completed with exit code 1.
|
|
wasm-js-tests (1.75)
Process completed with exit code 1.
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/builder.rs#L40
elided lifetime has a name
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/builder.rs#L23
the following explicit lifetimes could be elided: 'a
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/builder.rs#L66
the following explicit lifetimes could be elided: 'a
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/builder.rs#L76
the following explicit lifetimes could be elided: 'a
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/chunker.rs#L99
the following explicit lifetimes could be elided: 'a
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/chunker.rs#L108
the following explicit lifetimes could be elided: 'a
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/unixfs.rs#L267
the following explicit lifetimes could be elided: 'a
|
|
rust-checks (nightly):
wnfs-unixfs-file/src/unixfs.rs#L434
the following explicit lifetimes could be elided: 'a
|
|
rust-checks (nightly)
could not compile `wnfs-unixfs-file` (lib) due to 8 previous errors
|
|
rust-checks (nightly)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
|
rust-checks (1.75)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
rust-checks (1.75)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
rust-checks (1.75)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
|
rust-checks (1.75)
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/
|
|
rust-checks (1.75)
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/
|
|
rust-checks (1.75)
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/
|
|
rust-checks (1.75)
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/
|
|
wasm-js-tests (nightly)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
wasm-js-tests (nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
wasm-js-tests (nightly)
the following packages contain code that will be rejected by a future version of Rust: buf_redux v0.8.4, multipart v0.18.0
|
|
wasm-js-tests (1.75)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
wasm-js-tests (1.75)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
wasm-js-tests (1.75)
the following packages contain code that will be rejected by a future version of Rust: buf_redux v0.8.4, multipart v0.18.0
|
|
rust-checks (nightly)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
rust-checks (nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
rust-checks (nightly)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
|
rust-checks (nightly)
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/
|
|
rust-checks (nightly)
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/
|
|
rust-checks (nightly)
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/
|
|
rust-checks (nightly)
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/
|