max / makeover-webview

Follow makeover-layout to 0.44 and makeover-touch to 0.34 The vocabulary grew two members (quasicoherent 19d7602d). Nothing here reads them yet: `Node::Code` is quasi-router's and quasi-webview draws it, so what moves here is the pin.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MptwXZ8k65v19rFmdGAyki

Author: Max Johnson <me@maxj.phd> · 2026-09-02 15:28 UTC

Signed with PGP, not checked

Commit: 98a966ca3e7dad2c57dbefb5f17b16ebcdc9ca65

Parent: 6e3f297

1 file changed, +3 insertions, -3 deletions

M Cargo.toml +3 -3

			@@ -1,6 +1,6 @@
1	1		[package]
2	2		name = "makeover-webview"
3		-	version = "0.72.0"
	3	+	version = "0.73.0"
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.43"
	21	+	makeover-layout = "0.44"
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.
			@@ -28,7 +28,7 @@
28	28		# satisfies "0.8" and keeps a second makeover-geometry in the graph next to the
29	29		# 0.7 this crate asks for. `Density` is nominally distinct across the two and
30	30		# the build fails on a type that reads as identical.
31		-	makeover-touch = "0.33"
	31	+	makeover-touch = "0.34"
32	32		makeover-geometry = "0.7"
33	33
34	34		[lints.rust]