max / alloy_tui

Release 4.1.0 on the current makeover suite Moves makeover 2.3.0 -> 2.4.1 and makeover-tui 0.4.1 -> 0.5.1, the latter of which is the point: makeover-tui's old caret pin held makeover-layout at 0.4.0, and this crate was the path by which that reached GoingsOn. GO linked makeover-layout twice, 0.4.0 down this chain and 0.6.0 by way of makeover-webview, so the crate whose whole job is shared types had Depth and Fill present as two unrelated types in one binary. Minor rather than major despite a bumped public re-export: makeover-tui 0.5.1 carries no source change from 0.4.1, only its own dependency bump, so Fidelity is identical. Verified rather than assumed -- alloy and goingson both build and pass against this unchanged, and both now resolve a single makeover-layout 0.6.0.