0.65.0: follow makeover-layout to 0.43.0
The Bespoke split. `links = "makeover-layout"` forbids two copies of the
vocabulary in one graph, so a consumer cannot stay behind while the wave
lands, and 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>
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.71"
51
+
makeover-webview = "0.72"
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