Skip to main content

max / makeover-build

0.61.0: makeover-webview 0.68.0 The disabled arm states the rest look on both axes now, so a flat control gives its hover surface back and anything without a bevel gives back the pressed rule's inset one. A sheet generated from 0.67.0 leaves both.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session
https://claude.ai/code/session_01DwpiantpUgohzML4xr6KeQ
Author: Max Johnson <me@maxj.phd> · 2026-08-29 16:47 UTC
Signed with PGP, not checked
Commit: 4c9e1a13cc8f9d0017e385dd6002ef07974a0c9b
Parent: 877fce9
1 file changed, +7 insertions, -2 deletions
M Cargo.toml +7 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-build"
3 - version = "0.60.0"
3 + version = "0.61.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"
@@ -42,7 +42,12 @@
42 42 # declares nothing, so the generated layer held no rule for it and an app
43 43 # handing makeover the cascade with `revert-layer` rolled the handoff onto its
44 44 # own bare `button` rule. A generated sheet from 0.66.0 leaves that hole.
45 - makeover-webview = "0.67.0"
45 + #
46 + # 0.68.0 says it in the disabled arm too. Same hole one rule over: the arm
47 + # re-asserted only the axes its depth declares, so a flat control kept the
48 + # hover surface after it stopped answering, and anything without a bevel kept
49 + # the pressed rule's inset one.
50 + makeover-webview = "0.68.0"
46 51 makeover-geometry = "0.7"
47 52 # 0.1.1, not 0.1.0: the cadence axis and `reduced_motion_css` are what
48 53 # `timing_css` emits, and 0.1.0 has neither. A consumer resolving 0.1.0 would