Bump patch level for remaining crates
This is done because at the time of writing cargo-unleash does not fully support partial workspace publishing and mixes both local and crates.io versions of the packages, leading to errors in the release check workflow.
Showing
- Cargo.lock 120 additions, 120 deletionsCargo.lock
- client/api/Cargo.toml 1 addition, 1 deletionclient/api/Cargo.toml
- client/authority-discovery/Cargo.toml 1 addition, 1 deletionclient/authority-discovery/Cargo.toml
- client/basic-authorship/Cargo.toml 1 addition, 1 deletionclient/basic-authorship/Cargo.toml
- client/block-builder/Cargo.toml 1 addition, 1 deletionclient/block-builder/Cargo.toml
- client/chain-spec/Cargo.toml 1 addition, 1 deletionclient/chain-spec/Cargo.toml
- client/chain-spec/derive/Cargo.toml 1 addition, 1 deletionclient/chain-spec/derive/Cargo.toml
- client/consensus/aura/Cargo.toml 1 addition, 1 deletionclient/consensus/aura/Cargo.toml
- client/consensus/babe/Cargo.toml 1 addition, 1 deletionclient/consensus/babe/Cargo.toml
- client/consensus/babe/rpc/Cargo.toml 1 addition, 1 deletionclient/consensus/babe/rpc/Cargo.toml
- client/consensus/common/Cargo.toml 1 addition, 1 deletionclient/consensus/common/Cargo.toml
- client/consensus/epochs/Cargo.toml 1 addition, 1 deletionclient/consensus/epochs/Cargo.toml
- client/consensus/manual-seal/Cargo.toml 1 addition, 1 deletionclient/consensus/manual-seal/Cargo.toml
- client/consensus/pow/Cargo.toml 1 addition, 1 deletionclient/consensus/pow/Cargo.toml
- client/consensus/slots/Cargo.toml 1 addition, 1 deletionclient/consensus/slots/Cargo.toml
- client/consensus/uncles/Cargo.toml 1 addition, 1 deletionclient/consensus/uncles/Cargo.toml
- client/db/Cargo.toml 1 addition, 1 deletionclient/db/Cargo.toml
- client/executor/common/Cargo.toml 1 addition, 1 deletionclient/executor/common/Cargo.toml
- client/executor/wasmi/Cargo.toml 1 addition, 1 deletionclient/executor/wasmi/Cargo.toml
- client/executor/wasmtime/Cargo.toml 1 addition, 1 deletionclient/executor/wasmtime/Cargo.toml
Please register or sign in to comment