Skip to main content

max / makeover-build

0.60.0: makeover-webview 0.67.0 The renderer names the element-chrome reset and says flat out loud, so a generated layout.css now carries a rule for a facet value at rest. A sheet generated from 0.66.0 leaves that hole and an app handing makeover the cascade with revert-layer renders a described facet raised.
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:27 UTC
Signed with PGP, not checked
Commit: 877fce95b675a13f8ceacf5454b4161e5f65fd94
Parent: 07b5188
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.59.0"
3 + version = "0.60.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"
@@ -37,7 +37,12 @@
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.66.0"
40 + #
41 + # 0.67.0 says flat out loud. A facet value's rest depth is `Depth::Flat`, which
42 + # declares nothing, so the generated layer held no rule for it and an app
43 + # handing makeover the cascade with `revert-layer` rolled the handoff onto its
44 + # own bare `button` rule. A generated sheet from 0.66.0 leaves that hole.
45 + makeover-webview = "0.67.0"
41 46 makeover-geometry = "0.7"
42 47 # 0.1.1, not 0.1.0: the cadence axis and `reduced_motion_css` are what
43 48 # `timing_css` emits, and 0.1.0 has neither. A consumer resolving 0.1.0 would