From fa0f8a99007d38012deaabb6cb1dddc5d104229f Mon Sep 17 00:00:00 2001 From: meh Date: Thu, 3 Sep 2026 11:31:20 +0700 Subject: [PATCH] Release 0.5.6 on WorkTablesIndex 0.0.10 WorkTable and DataBucket exchange concrete WorkTablesIndex CDC types, and both pin that crate exactly, so the two pins are one decision. Bumping WorkTable to 0.0.10 without this resolves two versions of the same crate: WorkTablesIndex v0.0.9 via data_bucket 0.5.5 WorkTablesIndex v0.0.10 via worktable which are distinct Rust types even though the source is identical, and the build fails on `IndexValue<_>: From> is not satisfied`. That was reproduced, not predicted. 71 tests pass against 0.0.10 through a local path patch. **Merge after WorkTablesIndex#14**, which is what publishes 0.0.10. Until then this branch's CI cannot resolve its own dependency, and that failure is the ordering rather than a defect. --- Cargo.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Cargo.toml b/Cargo.toml index 07d69b9..3dd435c 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -3,7 +3,7 @@ members = ["codegen", "tools/create-data-file", "tools/dump-data-file"] [package] name = "data_bucket" -version = "0.5.5" +version = "0.5.6" edition = "2021" authors = ["Handy-caT"] license = "MIT" @@ -19,7 +19,7 @@ rkyv = { version = "0.8.17", features = ["uuid-1"] } uuid = { version = "1.11.0", features = ["v4"] } psc-nanoid = { version = "3.1.1", features = ["rkyv", "packed"] } ordered-float = "5.0.0" -indexset = { package = "WorkTablesIndex", version = "=0.0.9", default-features = false, features = ["concurrent", "cdc", "multimap"] } +indexset = { package = "WorkTablesIndex", version = "=0.0.10", default-features = false, features = ["concurrent", "cdc", "multimap"] } # indexset = { package = "wt-indexset", path = "../indexset", version = "0.12.10", features = ["concurrent", "cdc", "multimap"] } # indexset = { package = "wt-indexset", version = "0.12.12", features = ["concurrent", "cdc", "multimap"] } tokio = { version = "1", features = ["full"] }