Skip to main content

max / alloy_tui

Take the published makeover suite makeover-layout 0.29.1, makeover-webview 0.49.0, makeover-tui 0.29.0, makeover-immediate 0.29.0, makeover-touch 0.21.0, makeover-build 0.44.0, all on crates.io. The four whose own source did not change still took a minor: makeover-layout carries links, so one copy of the vocabulary per graph, and a consumer cannot take the old renderer and the new vocabulary together. Locks settle here because the crates.io [patch] block that carried the cascade is out of ~/Code/.cargo/config.toml. Getting to take it out is the check that the cascade actually finished.
Author: Max Johnson <me@maxj.phd> · 2026-08-18 20:01 UTC
Signed with PGP, not checked
Commit: e5722ace7aed2bb40751f2d74f9fa936ab378a16
Parent: 7f9490a
1 file changed, +1 insertion, -1 deletion
M Cargo.toml +1 -1
@@ -29,7 +29,7 @@
29 29 # semver boundary, so a stale pin here holds the whole console on an old
30 30 # renderer rather than resolving forward. `Fidelity` and `Theme` are re-exported
31 31 # from this crate, so the renderer's public types are part of ours.
32 - makeover-tui = { version = "0.28.0", features = ["theme"] }
32 + makeover-tui = { version = "0.29.0", features = ["theme"] }
33 33
34 34 [lints.rust]
35 35 unused = "warn"