max / makeover-webview

0.17.1: pin the makeover-layout minimum the radio actually needs form::radio_html calls FieldKind::Radio, which arrives in makeover-layout 0.8.2. The pin has said "0.8" since 0.16.1, where the radio landed, so a consumer whose lock already held 0.8.0 got a resolve that satisfied the pin and then failed to compile with "variant not found in FieldKind". Found from makeover-build, which is the crate the apps take in their build.rs and had exactly that lock.

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

Author: Max Johnson <me@maxj.phd> · 2026-08-06 17:02 UTC

Signed with PGP, not checked

Commit: a299c117131160729214e51435d3b8c953386534

Parent: d8d8e0f

1 file changed, +6 insertions, -2 deletions

M Cargo.toml +6 -2

			@@ -1,13 +1,17 @@
1	1		[package]
2	2		name = "makeover-webview"
3		-	version = "0.17.0"
	3	+	version = "0.17.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"
7	7		repository = "https://makenot.work/git/max/makeover-webview"
8	8
9	9		[dependencies]
10		-	makeover-layout = "0.8"
	10	+	# 0.8.2 and not 0.8: `form::radio_html` calls `FieldKind::Radio`, which arrives
	11	+	# in 0.8.2. Declared as "0.8" from 0.16.1, where the radio landed, so a consumer
	12	+	# whose lock already held 0.8.0 got a resolve that satisfied the pin and failed
	13	+	# to compile. makeover-build is where that surfaced, one release later.
	14	+	makeover-layout = "0.8.2"
11	15		# The capability axis. `makeover-touch` decides whether a hover rule should be
12	16		# gated at all; `makeover-geometry` spells the gate as a media condition. Both
13	17		# answers are owned elsewhere and neither is re-derived here.