Release 0.2.0, publishing three unshipped dependency bumps
The crate has been pinning newer makeover-webview since 0.7.0 without
ever going out, so crates.io still served 0.1.0 against webview ^0.1.0.
Version equality hid it: local and published both read 0.1.0 while the
source underneath had moved three times.
What that cost a consumer is the whole component set. The 0.1.0
generator emits a layout.css carrying .raised and .well and nothing
else, so the MNW server took this crate by path rather than from the
registry to get .button, .card, .field, .chip, .tab, .segment, .toggle,
.progress, .badge and .row at all.
Minor rather than patch: the emitted stylesheet changes substantially,
which is a behaviour change even though no signature moved. Also moves
the makeover floor to 2.4.1, the re-ramped parchment.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-07-31 17:36 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."