Take makeover-webview 0.63.0
The pin tracks the renderer half rather than this crate's own needs, as its own
comment says: this crate emits the stylesheet and the renderer emits the markup
that stylesheet matches, so a graph holding both at different versions is an app
whose CSS and HTML were generated by two crates that never agreed.
Behind it, makeover-layout 0.37.0 and Field::as_instant, which emits one
attribute and no CSS.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-28 15:02 UTC
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"
@@ -37,7 +37,7 @@
37
37
# a cell into a run of leaves, so "this text is a link" became a member the run
38
38
# holds rather than a field on one container, and the renderer needed a name for
39
39
# it that was not invented locally.
40
-
makeover-webview = "0.62.0"
40
+
makeover-webview = "0.63.0"
41
41
makeover-geometry = "0.7"
42
42
# 0.1.1, not 0.1.0: the cadence axis and `reduced_motion_css` are what
43
43
# `timing_css` emits, and 0.1.0 has neither. A consumer resolving 0.1.0 would