max / makeover-build

0.14.0: take makeover 2.5 and makeover-webview 0.22 The elevation intent, both halves. makeover-webview 0.22 emits --elevation-overlay referring to var(--elevation), and makeover 2.5 is what derives that token; neither crate can state the coupling, because makeover-webview has no dependency on makeover and that is deliberate. This manifest is the only one that sees both halves, so the floor goes here. Exact patch on makeover-webview for the reason 0.13.1 was released: a minor pin lets a consumer's lock keep an earlier patch that pins an older makeover-touch, which drags a second makeover-geometry into the graph.

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

Author: Max Johnson <me@maxj.phd> · 2026-08-10 14:49 UTC

Signed with PGP, not checked

Commit: 646a5879da496eb3ae37ad217ace8ef204e56574

Parent: 699e505

1 file changed, +15 insertions, -6 deletions

M Cargo.toml +15 -6

			@@ -1,17 +1,26 @@
1	1		[package]
2	2		name = "makeover-build"
3		-	version = "0.13.1"
	3	+	version = "0.14.0"
4	4		edition = "2024"
5	5		description = "Build-script support for the make-family design system: materialise makeover's themes and makeover-webview's stylesheet into a Tauri app's frontend, once, instead of copying the same twenty lines into every consumer's build.rs."
6	6		license = "MIT"
7	7		repository = "https://makenot.work/git/max/makeover-build"
8	8
9	9		[dependencies]
10		-	makeover = "2.4"
11		-	# 0.21.1 and not 0.21: an earlier 0.21 patch still pins makeover-touch 0.6, which
12		-	# drags a second makeover-geometry into the graph alongside the 0.7 below and
13		-	# fails to compile. The exact patch is what keeps the geometry axis single.
14		-	makeover-webview = "0.21.1"
	10	+	# 2.5 and not 2.4, because makeover-webview 0.22 emits `--elevation-overlay`
	11	+	# referring to `var(--elevation)`, and 2.5 is the release that derives that
	12	+	# token. The two crates cannot state the coupling themselves: makeover-webview
	13	+	# has no dependency on makeover, deliberately, so this is the only manifest that
	14	+	# sees both halves. A consumer resolving 2.4 here would generate a stylesheet
	15	+	# naming a token nothing defines, and a custom property whose value fails to
	16	+	# substitute takes the whole declaration with it rather than degrading.
	17	+	makeover = "2.5"
	18	+	# 0.22.0 and not 0.22: the same exact-patch discipline 0.13.1 was released for.
	19	+	# An earlier patch in a minor can pin an older makeover-touch, which drags a
	20	+	# second makeover-geometry into the graph alongside the one below and fails to
	21	+	# compile on `Density` being nominally distinct. The exact patch is what keeps
	22	+	# the geometry axis single.
	23	+	makeover-webview = "0.22.0"
15	24		makeover-geometry = "0.7"
16	25
17	26		[lints.rust]