Skip to main content

max / makeover-tui

0.14.1: take makeover-layout 0.15.0, so a TUI screen resolves the one the rest of the suite reads This was the last crate in the suite on 0.14.0. Nothing here matches on FieldKind, so 0.15.0's Date and DateTime need no rendering and this is a lockstep bump rather than an adoption. What it removes is the trap: a description layer renderer is meant to be swappable for the webview one, and until now taking both put two makeover-layouts in the graph, where Priority and Depth are nominally distinct types that read as identical.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-12 00:58 UTC
Signed with PGP, not checked
Commit: 93d957fa2176a5a345fc2e6e13f544ecf9587363
Parent: f7e2aaf
1 file changed, +2 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-tui"
3 - version = "0.14.0"
3 + version = "0.14.1"
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"
@@ -19,7 +19,7 @@
19 19 # compile against an API added in a later one -- which is what `Depth::Overlay`
20 20 # would do here. The rest of the suite has pinned this way since
21 21 # makeover-webview found it the hard way.
22 - makeover-layout = "0.14.0"
22 + makeover-layout = "0.15.0"
23 23 makeover = { version = "2.5", optional = true }
24 24
25 25 [lints.rust]