max / alloy_tui
1 file changed,
+7 insertions,
-2 deletions
| @@ -1,6 +1,6 @@ | |||
| 1 | 1 | [package] | |
| 2 | 2 | name = "alloy_tui" | |
| 3 | - | version = "7.1.0" | |
| 3 | + | version = "7.2.0" | |
| 4 | 4 | description = "Alloy design system: makeover intents rendered as ratatui Color/Style, plus themed widgets for the alloy console and siblings." | |
| 5 | 5 | edition = "2024" | |
| 6 | 6 | # 1.88 is ratatui 0.30.2's floor, and 0.30.2 is where `Block::shadow` lands. | |
| @@ -24,7 +24,12 @@ | |||
| 24 | 24 | # because this crate quantises a whole theme off `Fidelity::detect`, and before | |
| 25 | 25 | # that release an unrecognised TERM answered Ansi16, which cost a heavier frame | |
| 26 | 26 | # when the renderer was the only consumer and costs a flattened theme now. | |
| 27 | - | makeover-tui = { version = "0.26.0", features = ["theme"] } | |
| 27 | + | # | |
| 28 | + | # Pinned exactly, and moved in lockstep with the renderer: a 0.x minor is a | |
| 29 | + | # semver boundary, so a stale pin here holds the whole console on an old | |
| 30 | + | # renderer rather than resolving forward. `Fidelity` and `Theme` are re-exported | |
| 31 | + | # from this crate, so the renderer's public types are part of ours. | |
| 32 | + | makeover-tui = { version = "0.27.0", features = ["theme"] } | |
| 28 | 33 | ||
| 29 | 34 | [lints.rust] | |
| 30 | 35 | unused = "warn" |