max / makeover-build

Pin makeover-webview 0.75.1, which is the one that compiles 0.75.0 says `makeover-layout = "0.44"` and is written against 0.44.2's chart types and `Choice::chosen`, so a host whose lock already had 0.44.0 resolves it and fails. This crate calls none of that and still cannot take a version that cannot build.

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:03 UTC

Signed with PGP, not checked

Commit: 7948a9ab30b7f635fd6201ea468106acb9bd8107

Parent: fedc146

1 file changed, +5 insertions, -1 deletion

M Cargo.toml +5 -1

			@@ -48,7 +48,11 @@
48	48		# re-asserted only the axes its depth declares, so a flat control kept the
49	49		# hover surface after it stopped answering, and anything without a bevel kept
50	50		# the pressed rule's inset one.
51		-	makeover-webview = "0.75"
	51	+	# 0.75.1, not 0.75.0: 0.75.0 says `makeover-layout = "0.44"` and is written
	52	+	# against 0.44.2's chart types and `Choice::chosen`, so it resolves against an
	53	+	# older lock and does not compile. This crate does not call any of that and
	54	+	# still cannot take the version that cannot build.
	55	+	makeover-webview = "0.75.1"
52	56		makeover-geometry = "0.7"
53	57		# 0.1.1, not 0.1.0: the cadence axis and `reduced_motion_css` are what
54	58		# `timing_css` emits, and 0.1.0 has neither. A consumer resolving 0.1.0 would