Skip to main content

max / shop

Pin the makeover suite to current The suite went out today: makeover 2.4.1 (the re-ramped parchment), makeover-tui 0.5.1 and makeover-immediate 0.4.1 (both onto makeover-layout 0.6.0), makeover-build 0.2.0 and alloy_tui 4.1.0. The pins that mattered were the 0.x ones. A caret on 0.4.0 accepts nothing past 0.5, so the two renderers could never see layout 0.6 no matter how often the tree was rebuilt, where a caret on makeover 2.3.0 had been resolving to 2.4.1 all along and only read as stale.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-07-31 18:01 UTC
Signed with PGP, not checked
Commit: 47c9ef3fa91a92a5ce82c942df1cc56ff680266c
Parent: f4b5863
2 files changed, +3 insertions, -3 deletions
M Cargo.lock +2 -2
@@ -593,9 +593,9 @@
593 593
594 594 [[package]]
595 595 name = "makeover"
596 - version = "2.4.0"
596 + version = "2.4.1"
597 597 source = "registry+https://github.com/rust-lang/crates.io-index"
598 - checksum = "d19ed56441037cdf7c810eca04918cb320d065386e3b46a74e87fe69f966197d"
598 + checksum = "b0a796c931419e54dd71a8aaa7d62230730e958f3101d37d4c1d3ab7b541b38e"
599 599 dependencies = [
600 600 "include_dir",
601 601 "serde",
M Cargo.toml +1 -1
@@ -32,7 +32,7 @@
32 32 # text and page colours from a theme file rather than carrying a hex table, and
33 33 # `ansi_intent` is the mapping the bare Linux console and Alloy's generated
34 34 # configs use, so all three agree on what red means.
35 - makeover = "2.4.0"
35 + makeover = "2.4.1"
36 36 # For shop's own config file, and already in the tree underneath makeover.
37 37 toml = "1.1"
38 38