max / makenotwork

server: take makeover-layout 0.27.5 and makeover-build 0.39.0 Picks up the sort-caret unification: solid triangles everywhere, and an idle sortable heading drawn at content-secondary rather than reserving a hidden box. static/layout.css is generated and gitignored, so it regenerates on the next build.

Author: Max Johnson <me@maxj.phd> · 2026-08-16 22:01 UTC

Signed with PGP, not checked

Commit: 2ef29b84fa2b8e23b653d815fb086f073ee74882

Parent: 9a3cd19

1 file changed, +2 insertions, -2 deletions

M server/Cargo.toml +2 -2

			@@ -163,7 +163,7 @@
163	163		# rather than reached through quasi-router's re-export because a described
164	164		# screen names FieldKind and Tone directly; it has to track what quasi-router
165	165		# resolves or the two `layout::` paths are different crates.
166		-	makeover-layout = "0.27.0"
	166	+	makeover-layout = "0.27.5"
167	167		# For the request head the per-viewer state factory reads. axum re-exports it,
168	168		# but the factory's signature is quasi-axum's and names `http::request::Parts`.
169	169		http = "1.3.1"
			@@ -245,7 +245,7 @@
245	245		# Emits static/geometry.css (makeover-geometry) and static/layout.css
246	246		# (makeover-webview). The same generator GO and BB run; only the output paths
247	247		# differ, since the server serves its stylesheets rather than bundling them.
248		-	makeover-build = "0.38.0"
	248	+	makeover-build = "0.39.0"
249	249		# Read directly for the embeds' own copy of the spacing layer, which they need
250	250		# because an iframe cannot link a stylesheet. makeover-build does not re-export
251	251		# it, so the pin lives here and has to track the one makeover-build resolves.