Skip to main content

max / makeover-webview

0.22.1: pin makeover-touch to the exact patch touch 0.8.0 requires makeover-geometry ^0.6, so a consumer lock holding 0.8.0 satisfied "0.8" and kept a second makeover-geometry in the graph beside the 0.7 this crate asks for. The manifest already stated the exact-patch rule for makeover-layout and did not follow it here.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-10 15:09 UTC
Signed with PGP, not checked
Commit: 7f2b6219a44a7d5ca8549ee75d9030aad9f97eec
Parent: 20c97f0
1 file changed, +8 insertions, -2 deletions
M Cargo.toml +8 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-webview"
3 - version = "0.22.0"
3 + version = "0.22.1"
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"
@@ -16,7 +16,13 @@
16 16 # The capability axis. `makeover-touch` decides whether a hover rule should be
17 17 # gated at all; `makeover-geometry` spells the gate as a media condition. Both
18 18 # answers are owned elsewhere and neither is re-derived here.
19 - makeover-touch = "0.8"
19 + #
20 + # Exact patch, for the second reason a minor-only pin is wrong: touch 0.8.0
21 + # requires makeover-geometry ^0.6, so a consumer lock already holding 0.8.0
22 + # satisfies "0.8" and keeps a second makeover-geometry in the graph next to the
23 + # 0.7 this crate asks for. `Density` is nominally distinct across the two and
24 + # the build fails on a type that reads as identical.
25 + makeover-touch = "0.8.1"
20 26 makeover-geometry = "0.7"
21 27
22 28 [lints.rust]