max / makenotwork

Take makeover-webview 0.76 and makeover-build 0.69 Tracking the cascade rather than reaching for anything new in either. Both carry the same reason: makeover-webview declares `links`, so this crate and quasi-webview holding different versions of it between them is a resolver error rather than a warning, and quasi-webview moved.

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

Signed with PGP, not checked

Commit: 4774b56b25c7db9a93d984ea14a2e105aaa3e586

Parent: 642fc66

1 file changed, +2 insertions, -2 deletions

M server/Cargo.toml +2 -2

			@@ -179,7 +179,7 @@
179	179		# through quasi-webview for makeover-layout's reason: two `form::` paths from
180	180		# two resolutions are two crates, and the `data-format="markdown"` rules in
181	181		# `static/layout.css` are generated from this one.
182		-	makeover-webview = "0.75.1"
	182	+	makeover-webview = "0.76"
183	183		# For the request head the per-viewer state factory reads. axum re-exports it,
184	184		# but the factory's signature is quasi-axum's and names `http::request::Parts`.
185	185		http = "1.3.1"
			@@ -265,7 +265,7 @@
265	265		# Emits static/geometry.css (makeover-geometry) and static/layout.css
266	266		# (makeover-webview). The same generator GO and BB run; only the output paths
267	267		# differ, since the server serves its stylesheets rather than bundling them.
268		-	makeover-build = "0.68"
	268	+	makeover-build = "0.69"
269	269		# Read directly for the embeds' own copy of the spacing layer, which they need
270	270		# because an iframe cannot link a stylesheet. makeover-build does not re-export
271	271		# it, so the pin lives here and has to track the one makeover-build resolves.