0.20.2: take makeover-webview 0.26.0
A pin bump and nothing else. The generated stylesheet is byte-identical, because
0.26.0 adds two input types and changes no CSS.
It is not cosmetic. This manifest is the only one stating the coupling between
the design crates, so a consumer that had taken makeover-layout 0.15.0 directly
resolved two makeover-webviews and two makeover-layouts: the sheet generated at
build time from 0.25.1, the screens rendered at runtime from 0.26.0. They agree
today and nobody should have to check that they still do.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-11 23:07 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"
@@ -20,7 +20,7 @@
20
20
# second makeover-geometry into the graph alongside the one below and fails to
21
21
# compile on `Density` being nominally distinct. The exact patch is what keeps