max / alloy_tui

Follow the makeover 0.44 and quasi 0.99 wave makeover-layout grew `Syntax` and `Change` (quasicoherent 19d7602d), and makeover-layout carries `links`, so every pin in the graph moves together or two copies of the vocabulary is a resolver error rather than a warning. Nothing here reads the new members yet.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MptwXZ8k65v19rFmdGAyki

Author: Max Johnson <me@maxj.phd> · 2026-09-02 15:31 UTC

Signed with PGP, not checked

Commit: 567213c1a4871590eb58decf2485d216316e9016

Parent: fb377be

1 file changed, +1 insertion, -1 deletion

M Cargo.toml +1 -1

			@@ -30,7 +30,7 @@
30	30		# semver boundary, so a stale pin here holds the whole console on an old
31	31		# renderer rather than resolving forward. `Fidelity` and `Theme` are re-exported
32	32		# from this crate, so the renderer's public types are part of ours.
33		-	makeover-tui = { version = "0.43", features = ["theme"] }
	33	+	makeover-tui = { version = "0.44", features = ["theme"] }
34	34
35	35		[lints.rust]
36	36		unused = "warn"