max / alloy_tui

Take makeover-geometry from the registry, not the tree 0.1.0 is on crates.io and the published copy is byte-identical to ../makeover-geometry, so the path dep bought nothing and would have hidden a divergence if one appeared. The makeover patch below stays: that one is genuinely ahead of its release.

Author: Max Johnson <me@maxj.phd> · 2026-07-27 02:24 UTC

Signed with PGP, not checked

Commit: 8210f161018b225f0b0ba666e2e622adae12b51a

Parent: 7debcaf

1 file changed, +4 insertions, -4 deletions

M Cargo.toml +4 -4

			@@ -12,10 +12,10 @@
12	12		[dependencies]
13	13		ratatui = "0.30"
14	14		makeover = "2.1.0"
15		-	# Unpublished. A path dep with a version means local builds resolve to the tree
16		-	# and `cargo publish` refuses until 0.1.0 is actually on crates.io, which is the
17		-	# gate we want: this crate cannot ship depending on something nobody can fetch.
18		-	makeover-geometry = { version = "0.1.0", path = "../makeover-geometry" }
	15	+	# Published, and no patch stanza: unlike makeover below, the registry copy of
	16	+	# 0.1.0 is byte-identical to the tree, so a path dep would buy nothing and hide
	17	+	# a divergence if one ever appeared.
	18	+	makeover-geometry = "0.1.0"
19	19
20	20		# TEMPORARY. The bevel intents and the 256-color palette are in makeover's tree
21	21		# and not yet on crates.io. Remove this the moment makeover publishes them, and