Skip to main content

max / makeover-touch

0.8.3: track makeover-layout 0.15.0 The pin this line's own comment warns about had lagged again. This crate re-exports makeover_layout::Priority, so a stale requirement does not merely lag: it resolves a second makeover-layout beside the one the consumer asked for, and the two Priorities are nominally distinct types. Measured in the MNW server after it took makeover-layout 0.15.0 directly: the lock carried 0.14.0 and 0.15.0 at once, and this manifest was the only thing holding the older one.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-11 23:09 UTC
Signed with PGP, not checked
Commit: b4b2c8a1bf627ef3046f7feebb3323eb80174de2
Parent: 6286ebf
1 file changed, +2 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-touch"
3 - version = "0.8.2"
3 + version = "0.8.3"
4 4 edition = "2024"
5 5 description = "The adaptation layer of the make-family design system: which affordances exist at a given input class and window size class. Names what appears and disappears, never how much space it takes."
6 6 license = "MIT"
@@ -13,7 +13,7 @@
13 13 # it resolves a SECOND makeover-layout beside the one the consumer asked for,
14 14 # and the two Priorities are nominally distinct. makeover-webview takes both
15 15 # crates and was carrying 0.12 and 0.14 at once because of this line.
16 - makeover-layout = "0.14.0"
16 + makeover-layout = "0.15.0"
17 17
18 18 [lints.rust]
19 19 unused = "warn"