Take makeover-webview 0.74
Carries the requirement forward, so a consumer cannot end up with this crate
asking for the new stylesheet and its own pin holding the old one. A minor
bump rather than a patch for the reason the `links` key exists: two versions
of the renderer in one graph is a resolver error, so the requirement moving is
a fact every consumer has to be told.
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.73"
51
+
makeover-webview = "0.74"
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