Skip to main content

max / makeover-build

0.8.0: take makeover-webview 0.16 The last stale pin in the suite, and the one that kept the others stale for everyone downstream: this crate is what the apps take in their build.rs, so a webview pin here reaches every consumer whether or not that consumer names makeover-webview itself. goingson is the case that found it. After repinning webview, layout and tui directly it still resolved two copies of makeover-layout, because this crate was pulling webview 0.13 -> layout 0.7 in behind them. One pin, three crates downstream of it. Nothing here changes. Every bump in the chain (touch 0.4.0, tui 0.8.0, webview 0.16.0) is itself a pin bump; layout 0.8.0 is where the actual change was.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-05 19:08 UTC
Signed with PGP, not checked
Commit: 97cb0ff974bb66d9013d4e31677e4719acd40b91
Parent: 868b628
1 file changed, +2 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-build"
3 - version = "0.7.0"
3 + version = "0.8.0"
4 4 edition = "2024"
5 5 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"
@@ -8,7 +8,7 @@
8 8
9 9 [dependencies]
10 10 makeover = "2.4.1"
11 - makeover-webview = "0.13"
11 + makeover-webview = "0.16"
12 12 makeover-geometry = "0.6"
13 13
14 14 [lints.rust]