chore(namada): namada 0.41.0 -> namada_tx 0.42.0 #2193
Annotations
1 error and 20 warnings
build website
Command pnpm recursive install --frozen-lockfile --strict-peer-dependencies (cwd: undefined) exits with status 1
|
build website
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1, pnpm/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build website
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1, mozilla-actions/[email protected], actions-rs/cargo@v1, pnpm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build website:
crates/fadroma-dsl/src/attr.rs#L47
`&` without an explicit lifetime name cannot be used here
|
build website:
crates/fadroma-dsl/src/attr.rs#L49
`&` without an explicit lifetime name cannot be used here
|
build website:
crates/fadroma-dsl/src/attr.rs#L51
`&` without an explicit lifetime name cannot be used here
|
build website:
crates/fadroma-dsl/src/attr.rs#L52
`&` without an explicit lifetime name cannot be used here
|
build website:
crates/fadroma-dsl/src/attr.rs#L53
`&` without an explicit lifetime name cannot be used here
|
build website:
crates/fadroma-dsl/src/attr.rs#L54
`&` without an explicit lifetime name cannot be used here
|
build website:
crates/fadroma-dsl/src/attr.rs#L55
`&` without an explicit lifetime name cannot be used here
|
build website:
crates/fadroma-dsl/src/validate.rs#L13
field `value` is never read
|
build website:
crates/fadroma-derive-canonize/src/common.rs#L59
variable does not need to be mutable
|
build website:
crates/fadroma-derive-canonize/src/common.rs#L65
variable does not need to be mutable
|
build website
command pnpm store prune exits with code 1
|
build website
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/
|
build website
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/
|
build website
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/
|
build website
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/
|
build website
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/
|
build website
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/
|
build website
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/
|