Skip to main content

max / makeover-tui

Bump to 0.34.0: 0.33.0 is published and this tree is not it 850b029 moved this crate to makeover-layout 0.35.0 while the manifest still said 0.33.0, which is on crates.io. One version number naming two different crates is what problem 87a7a4d1 exists to kill. Minor rather than patch, because the change reaches consumers. lib.rs:198 is `pub use makeover_layout;`, so the whole crate is re-exported, and makeover-layout is 0.x where 0.34 to 0.35 is itself breaking. A consumer pairing this with makeover-layout 0.34 does not compile. Consumers stay on 0.33.0 deliberately. There is no [patch] entry for the makeover suite in ~/Code/.cargo/config.toml, so they resolve from crates.io and pointing them at an unpublished 0.34.0 would break every one of their builds. The forward-fix is owed at publish time, not now: magicmirror, mnw-cli, alloy_tui, memarkable, spaghetti, goingson (workspace, got inherits), quasi-tui, quasi-bench.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-23 23:19 UTC
Signed with PGP, not checked
Commit: 99b078f47b1392ae6e7099c620c714bb9d687951
Parent: 850b029
1 file changed, +1 insertion, -1 deletion
M Cargo.toml +1 -1
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-tui"
3 - version = "0.33.0"
3 + version = "0.34.0"
4 4 edition = "2024"
5 5 description = "The terminal renderer for makeover-layout, on ratatui. Colour stops being the constraint above 256 entries; geometry never does, because an edge occupies a whole cell on every side."
6 6 license = "MIT"