Skip to main content

max / makeover-webview

Say the makeover-layout version this actually needs `makeover-layout = "0.44"` resolved 0.44.2 here and 0.44.0 on a host whose lock already had one, where `Bar`, `Chart` and `Choice::chosen` do not exist and the crate does not compile. Found by makeover-build's publish, which is a fresh checkout with an older lock. The requirement now states what the code is written against, which is the same rule the tree applies to its own cross-repo pins one level up.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session
https://claude.ai/code/session_01P8ostB2UmZJGj5WjSHRSot
Author: Max Johnson <me@maxj.phd> · 2026-09-08 21:02 UTC
Signed with PGP, not checked
Commit: 32fcb8e9463a9492e24452dcfad32ca79f6461b6
Parent: 9fe53b5
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.75.0"
3 + version = "0.75.1"
4 4 edition = "2024"
5 5 # One copy of this renderer per dependency graph, enforced by cargo rather than
6 6 # by remembering. Two versions means the generated stylesheet and the emitted
@@ -18,7 +18,7 @@
18 18 # patch satisfy the requirement and still fail to compile. That happened once
19 19 # with `form::radio_html` calling `FieldKind::Radio`, and makeover-build is where
20 20 # it surfaced, one release later.
21 - makeover-layout = "0.44"
21 + makeover-layout = "0.44.2"
22 22 # The capability axis. `makeover-touch` decides whether a hover rule should be
23 23 # gated at all; `makeover-geometry` spells the gate as a media condition. Both
24 24 # answers are owned elsewhere and neither is re-derived here.