max / makeover-touch

0.8.2: take makeover-layout 0.14.0, so a consumer holds one description and not two This crate re-exports makeover_layout::Priority, so the requirement here is not a private matter. At "0.12" against a suite on 0.14 it resolved a second makeover-layout beside the one the consumer asked for, and the two Priorities are nominally distinct -- the same shape as the makeover-geometry duplication the exact-patch discipline was written for, one crate over. makeover-webview takes both crates and was compiling 0.12 and 0.14 at once. Exact patch now, with the reason on the line, so the next reader does not relax it back to a minor.

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

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

Signed with PGP, not checked

Commit: 6286ebf342744a1a89b0977b2cdc9b1a495821f0

Parent: 0a7cca6

1 file changed, +7 insertions, -2 deletions

M Cargo.toml +7 -2

			@@ -1,6 +1,6 @@
1	1		[package]
2	2		name = "makeover-touch"
3		-	version = "0.8.1"
	3	+	version = "0.8.2"
4	4		edition = "2024"
5	5		description = "The adaptation layer of the make-family design system: which affordances exist at a given input class and window size class. Names what appears and disappears, never how much space it takes."
6	6		license = "MIT"
			@@ -8,7 +8,12 @@
8	8
9	9		[dependencies]
10	10		makeover-geometry = "0.7"
11		-	makeover-layout = "0.12"
	11	+	# Exact patch, and it must track the suite. This crate re-exports
	12	+	# `makeover_layout::Priority`, so a stale requirement here does not merely lag:
	13	+	# it resolves a SECOND makeover-layout beside the one the consumer asked for,
	14	+	# and the two Priorities are nominally distinct. makeover-webview takes both
	15	+	# crates and was carrying 0.12 and 0.14 at once because of this line.
	16	+	makeover-layout = "0.14.0"
12	17
13	18		[lints.rust]
14	19		unused = "warn"