max / alloy_tui

14.0.0: follow makeover-layout to 0.43.0 The Bespoke split. `links = "makeover-layout"` forbids two copies of the vocabulary in one graph, so a consumer cannot stay behind while the wave lands, and the requirement change is breaking for anything downstream of this crate whatever else did or did not change here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MptwXZ8k65v19rFmdGAyki

Author: Max Johnson <me@maxj.phd> · 2026-09-01 22:06 UTC

Signed with PGP, not checked

Commit: fb377be2222719a174fa61e7d070a1e75f04557a

Parent: 47da1b3

1 file changed, +2 insertions, -2 deletions

M Cargo.toml +2 -2

			@@ -1,6 +1,6 @@
1	1		[package]
2	2		name = "alloy_tui"
3		-	version = "13.0.0"
	3	+	version = "14.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.
			@@ -30,7 +30,7 @@
30	30		# semver boundary, so a stale pin here holds the whole console on an old
31	31		# renderer rather than resolving forward. `Fidelity` and `Theme` are re-exported
32	32		# from this crate, so the renderer's public types are part of ours.
33		-	makeover-tui = { version = "0.42", features = ["theme"] }
	33	+	makeover-tui = { version = "0.43", features = ["theme"] }
34	34
35	35		[lints.rust]
36	36		unused = "warn"