max / alloy_tui

Take makeover 3.0 and makeover-tui 0.28 Major because makeover types are in this crate's public API, so a consumer cannot pair a new alloy_tui with the old makeover.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-18 14:32 UTC

Signed with PGP, not checked

Commit: 7f9490a87eaeebd1c7dda81c3daefe18e0cd5768

Parent: 6cfd746

1 file changed, +3 insertions, -3 deletions

M Cargo.toml +3 -3

			@@ -1,6 +1,6 @@
1	1		[package]
2	2		name = "alloy_tui"
3		-	version = "7.2.0"
	3	+	version = "8.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.
			@@ -15,7 +15,7 @@
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.5.0"
	18	+	makeover = "3.0"
19	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
			@@ -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.27.0", features = ["theme"] }
	32	+	makeover-tui = { version = "0.28.0", features = ["theme"] }
33	33
34	34		[lints.rust]
35	35		unused = "warn"