max / makeover-tui

Say the makeover-layout version this actually needs Declared "0.44" while being written against 0.44.2s Bar, Chart and Choice::chosen, so it resolves fine against a fresh index and fails against any lock that already held 0.44.0. alloy_tui's pre-push hook is where it surfaced: a consumer that touches none of that API still could not build. Third instance of this defect today after makeover-webview 0.75.0 and its knock-on in makeover-build, which is why makeover bb072566 exists.

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

Author: Max Johnson <me@maxj.phd> · 2026-09-08 21:28 UTC

Signed with PGP, not checked

Commit: ebc7156651951a5acf727f2c4bb251b51d0a9910

Parent: e8857d9

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.44.1"
	3	+	version = "0.44.2"
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"
			@@ -20,7 +20,7 @@
20	20		# compile against an API added in a later one -- which is what `Depth::Overlay`
21	21		# would do here. The rest of the suite has pinned this way since
22	22		# makeover-webview found it the hard way.
23		-	makeover-layout = "0.44"
	23	+	makeover-layout = "0.44.2"
24	24		# The cadence the activity mark blinks at, and the motion-off seam beside it.
25	25		# Taken rather than chosen here: `activity_lit` is this crate's only use of it,
26	26		# and the whole point is that the number is not this crate's to pick.