max / makeover-webview

Take makeover-layout 0.27.0 Region::Group. No code change here: this crate matches on intents rather than on Region, so the new member arrives through the vocabulary and the bump is the whole of it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-15 19:46 UTC

Signed with PGP, not checked

Commit: 83a4c7aedbde55eae37afa136ebb2c4458f6994d

Parent: 7d59fc3

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.44.0"
	3	+	version = "0.45.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
			@@ -17,7 +17,7 @@
17	17		# patch satisfy the requirement and still fail to compile. That happened once
18	18		# with `form::radio_html` calling `FieldKind::Radio`, and makeover-build is where
19	19		# it surfaced, one release later.
20		-	makeover-layout = "0.26.1"
	20	+	makeover-layout = "0.27.0"
21	21		# The capability axis. `makeover-touch` decides whether a hover rule should be
22	22		# gated at all; `makeover-geometry` spells the gate as a media condition. Both
23	23		# answers are owned elsewhere and neither is re-derived here.
			@@ -27,7 +27,7 @@
27	27		# satisfies "0.8" and keeps a second makeover-geometry in the graph next to the
28	28		# 0.7 this crate asks for. `Density` is nominally distinct across the two and
29	29		# the build fails on a type that reads as identical.
30		-	makeover-touch = "0.18.0"
	30	+	makeover-touch = "0.19.0"
31	31		makeover-geometry = "0.7"
32	32
33	33		[lints.rust]