Skip to main content

max / makeover-build

0.64.0: follow makeover-layout to 0.42.0 `links = "makeover-layout"` forbids two copies of the vocabulary in one graph, so every consumer moves in the same wave rather than at its own pace. Minor bump because the requirement change is breaking for anything downstream of this crate, whatever else did or did not change here.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session
https://claude.ai/code/session_01MptwXZ8k65v19rFmdGAyki
Author: Max Johnson <me@maxj.phd> · 2026-09-01 21:03 UTC
Signed with PGP, not checked
Commit: 23762f4b3db0b3b0e59876e578cfc32fce3e5ed0
Parent: e3e0355
1 file changed, +2 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-build"
3 - version = "0.63.1"
3 + version = "0.64.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"
@@ -48,7 +48,7 @@
48 48 # re-asserted only the axes its depth declares, so a flat control kept the
49 49 # hover surface after it stopped answering, and anything without a bevel kept
50 50 # the pressed rule's inset one.
51 - makeover-webview = "0.70.0"
51 + makeover-webview = "0.71"
52 52 makeover-geometry = "0.7"
53 53 # 0.1.1, not 0.1.0: the cadence axis and `reduced_motion_css` are what
54 54 # `timing_css` emits, and 0.1.0 has neither. A consumer resolving 0.1.0 would