0.59.0: makeover-webview 0.66.0
The last step of the makeover-layout 0.39.0 cascade, and the one that was
missing: layout 0.39.0, webview 0.66.0, immediate 0.40.0 and tui 0.39.0 were all
published and this still pinned webview 0.65.0. Nothing downstream could move,
because webview 0.65 wants layout ^0.38 and `makeover-layout` carries `links` --
so a consumer taking both this and the new layout got a resolver error rather
than a warning, and every Tauri app's build.rs takes this.
No code change. The generated stylesheet grows `.form-option-detail` with
webview 0.66.0, which is `Choice::detail` drawn: a consumer's dead-vocabulary
count rises by one until a described screen there spells one.
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"
@@ -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.65.0"
40
+
makeover-webview = "0.66.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