Skip to main content

max / makeover-webview

0.16.0: take makeover-touch 0.4 0.15.0 moved this crate to makeover-layout 0.8 and left makeover-touch on 0.3, which still takes layout 0.7 -- so 0.15.0 resolves two copies of the description inside its own graph. It compiles, because no layout type crosses the boundary between this crate and touch today, and that is luck rather than design. This is the failure mode 0.14.0's own commit message described and then walked into one release later: the pin cannot lag behind a sibling minor even when nothing here needs anything from it. Nothing here changes. makeover-touch 0.4.0 is itself a pin bump.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-05 19:07 UTC
Signed with PGP, not checked
Commit: b1161c104042baf98c9cdfe10acd20aa1b6099ea
Parent: 456bf2f
1 file changed, +2 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-webview"
3 - version = "0.15.0"
3 + version = "0.16.0"
4 4 edition = "2024"
5 5 description = "The webview renderer for makeover-layout. Emits CSS, and is the one renderer that needs no palette: var() is the late binding, so resolution stays with the browser."
6 6 license = "MIT"
@@ -11,7 +11,7 @@
11 11 # The capability axis. `makeover-touch` decides whether a hover rule should be
12 12 # gated at all; `makeover-geometry` spells the gate as a media condition. Both
13 13 # answers are owned elsewhere and neither is re-derived here.
14 - makeover-touch = "0.3"
14 + makeover-touch = "0.4"
15 15 makeover-geometry = "0.6"
16 16
17 17 [lints.rust]