max / makeover-touch

0.24.0: take makeover-layout 0.34.0 No code change. `makeover-layout` carries `links`, so one graph may hold exactly one copy of it and a consumer left on the old requirement is a resolver error rather than a warning: makeover-webview asking for 0.34.0 while this asks for 0.33.0 fails to resolve at all. The pin moves with the cascade or nothing downstream builds.

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

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

Signed with PGP, not checked

Commit: 58025f0ec4b2dbc3601a23d74ee65a671a4fbe16

Parent: fc534f1

1 file changed, +2 insertions, -2 deletions

M Cargo.toml +2 -2

			@@ -1,6 +1,6 @@
1	1		[package]
2	2		name = "makeover-touch"
3		-	version = "0.23.0"
	3	+	version = "0.24.0"
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"
			@@ -13,7 +13,7 @@
13	13		# it resolves a SECOND makeover-layout beside the one the consumer asked for,
14	14		# and the two Priorities are nominally distinct. makeover-webview takes both
15	15		# crates and was carrying 0.12 and 0.14 at once because of this line.
16		-	makeover-layout = "0.33.0"
	16	+	makeover-layout = "0.34.0"
17	17
18	18		[lints.rust]
19	19		unused = "warn"