Skip to main content

max / alloy_tui

Take the current makeover suite makeover 2.5.0, makeover-geometry 0.7, makeover-tui 0.12.0. alloy's two consumers (alloy, skelgen) compile against it unchanged.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-10 15:29 UTC
Signed with PGP, not checked
Commit: 558785dfb2c4fa82d30674bd136eb21f061b3a08
Parent: b9c91d0
1 file changed, +3 insertions, -3 deletions
M Cargo.toml +3 -3
@@ -15,8 +15,8 @@
15 15 # both of which this crate resolves at load. A [patch.crates-io] stanza stood
16 16 # here while they were unpublished; it is gone, and so is the last reason this
17 17 # crate could not be published from a clean checkout.
18 - makeover = "2.4.1"
19 - makeover-geometry = "0.6"
18 + makeover = "2.5.0"
19 + makeover-geometry = "0.7"
20 20 # The family's terminal renderer, which owns the bevel painting, the fill, and
21 21 # the reading of what the terminal can show. 0.4.0 and not 0.3.0 because the
22 22 # half-block glyphs are what makes delegating here an improvement rather than a
@@ -24,7 +24,7 @@
24 24 # because this crate quantises a whole theme off `Fidelity::detect`, and before
25 25 # that release an unrecognised TERM answered Ansi16, which cost a heavier frame
26 26 # when the renderer was the only consumer and costs a flattened theme now.
27 - makeover-tui = { version = "0.8.0", features = ["theme"] }
27 + makeover-tui = { version = "0.12.0", features = ["theme"] }
28 28
29 29 [lints.rust]
30 30 unused = "warn"