On 2025-05-09, we released version 1.1.2 of all our crates, which contained this critical bugfix. It was unfortunate that we then also needed to push a new CLI version, as the bug was entirely within the bindings crate (or in fact, its Cargo.toml metadata). If the default spacetime init --lang rust template depended on spacetimedb = "X.Y" rather than spacetimedb = "X.Y.Z", we would not have needed to release a new CLI version.
We could also consider weakening our crates' in-workspace dependencies in the same way. That way, we could have released only spacetimedb (aka bindings), where in practice we had to release all of its in-workspace dependencies (lib, sats, bindings-sys, bindings-macro, &c) because bindings depended on exactly version 1.1.2 of those crates.
On 2025-05-09, we released version 1.1.2 of all our crates, which contained this critical bugfix. It was unfortunate that we then also needed to push a new CLI version, as the bug was entirely within the bindings crate (or in fact, its Cargo.toml metadata). If the default
spacetime init --lang rusttemplate depended onspacetimedb = "X.Y"rather thanspacetimedb = "X.Y.Z", we would not have needed to release a new CLI version.We could also consider weakening our crates' in-workspace dependencies in the same way. That way, we could have released only
spacetimedb(akabindings), where in practice we had to release all of its in-workspace dependencies (lib,sats,bindings-sys,bindings-macro, &c) becausebindingsdepended on exactly version 1.1.2 of those crates.