@@ -7,7 +7,7 @@ members = ["crates/*", "bridge/*"]
77# parallel linker processes to race on the same output file (LNK1104).
88# `members` still contains bridge/* so workspace-wide commands
99# (`cargo test --workspace`, `cargo clippy --workspace`) keep covering it.
10- default-members = [" crates/cli" , " crates/core" , " crates/node" , " crates/rust" , " crates/python" , " crates/testkit " , " bridge/node" ]
10+ default-members = [" crates/cli" , " crates/core" , " crates/node" , " crates/rust" , " crates/python" , " bridge/node" ]
1111
1212[workspace .package ]
1313edition = " 2024"
@@ -24,12 +24,11 @@ categories = ["development-tools"]
2424# Internal — `version` is required so `cargo publish` can resolve path
2525# dependencies against crates.io. When bumping any crate version, remember
2626# to update these entries in lockstep.
27- dependency-check-updates-core = { path = " crates/core" , version = " 0.1.4" }
28- dependency-check-updates-node = { path = " crates/node" , version = " 0.1.4" }
29- dependency-check-updates-rust = { path = " crates/rust" , version = " 0.1.4" }
30- dependency-check-updates-python = { path = " crates/python" , version = " 0.1.4" }
31- dependency-check-updates = { path = " crates/cli" , version = " 0.1.4" }
32- dependency-check-updates-testkit = { path = " crates/testkit" , version = " 0.1.4" }
27+ dependency-check-updates-core = { path = " crates/core" }
28+ dependency-check-updates-node = { path = " crates/node" }
29+ dependency-check-updates-rust = { path = " crates/rust" }
30+ dependency-check-updates-python = { path = " crates/python" }
31+ dependency-check-updates = { path = " crates/cli" }
3332
3433# External
3534clap = { version = " 4.6" , features = [" derive" ] }
0 commit comments