Skip to main content

max / makeover-immediate

Release 0.4.0 on makeover-layout 0.6.0 The pin was caret ^0.4.0, so 0.5 and 0.6 were invisible to it and the renderer sat two breaking releases behind the description it renders. That is what put two incompatible copies of makeover-layout into GoingsOn at once, 0.4.0 by way of the renderers and 0.6.0 by way of makeover-webview, which for a crate whose whole job is shared types means Depth and Fill existing twice as unrelated types in one binary. Nothing needed changing to compile: 0.5.0 and 0.6.0 only widened enums to non_exhaustive, and the sunken work in 476b2ec had already taught this crate to answer an unknown fill rather than match exhaustively. Minor rather than patch: paint_bevel takes makeover_layout::Bevel in its signature, so the dependency's version is this crate's public API.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-07-31 17:44 UTC
Signed with PGP, not checked
Commit: c6056c0ffb83439b03e9eb437e8849fbec848fd3
Parent: 9bf09d3
1 file changed, +2 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-immediate"
3 - version = "0.3.0"
3 + version = "0.4.0"
4 4 edition = "2024"
5 5 description = "The immediate-mode renderer for makeover-layout. Immediate mode is the constraint that matters, not the library: no cascade, no retained tree, one stroke per widget. Backed by egui."
6 6 license = "MIT"
@@ -8,7 +8,7 @@
8 8
9 9 [dependencies]
10 10 egui = { version = "0.35", default-features = false }
11 - makeover-layout = "0.4.0"
11 + makeover-layout = "0.6.0"
12 12
13 13 [lints.rust]
14 14 unused = "warn"