Skip to main content

max / alloy_tui

Take makeover-tui 0.18.0 and call border-strong a focus ring makeover_tui types are in this crate's public API, so the incompatible dep bump is breaking here too: 6.0.0 -> 7.0.0.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-13 13:54 UTC
Signed with PGP, not checked
Commit: ef6d03ee6ea3eb483b81cb6d7b34ad0fcba989e2
Parent: 1c2607c
2 files changed, +4 insertions, -3 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "alloy_tui"
3 - version = "6.0.0"
3 + version = "7.0.0"
4 4 description = "Alloy design system: makeover intents rendered as ratatui Color/Style, plus themed widgets for the alloy console and siblings."
5 5 edition = "2024"
6 6 # 1.88 is ratatui 0.30.2's floor, and 0.30.2 is where `Block::shadow` lands.
@@ -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.17.0", features = ["theme"] }
27 + makeover-tui = { version = "0.18.0", features = ["theme"] }
28 28
29 29 [lints.rust]
30 30 unused = "warn"
M src/theme.rs +2 -1
@@ -20,7 +20,8 @@
20 20 //! makeover emits a `border-strong` too, and [`makeover_tui::Theme`] carries it:
21 21 //! a flat 5% darkening of the authored border, a slightly firmer divider. Alloy's
22 22 //! is pulled most of the way to the text colour because DESIGN-LANGUAGE.md makes
23 - //! it the entire focus cue and TOKENS.md holds it to WCAG AA-UI against the page.
23 + //! it Alloy's entire focus ring and TOKENS.md holds it to WCAG AA-UI against the
24 + //! page.
24 25 //! On Akari Dawn the two land at 3.27:1 and 1.63:1. They are different tokens
25 26 //! wearing one name, and adopting the shared one would take focus to half the
26 27 //! required floor.