Take the template's makeover pins off a set that cannot resolve
makeover-build 0.49 reaches makeover-layout ^0.33 through makeover-webview
0.55, and makeover-tui 0.33 requires ^0.35. makeover-layout carries a links
key, so two versions in one graph is a resolver error rather than a warning
and a generated app resolved neither.
0.51.0 and 0.34.0 agree on makeover-layout 0.35 and are what the registry
has. Measured by resolving a generated app outside ~/Code, which is the only
place these manifests are read: the workspace excludes the template, so
cargo check never sees them, and the conflict was masked until the quasi
requirements ahead of it were satisfiable.
- Co-Authored-By
- Claude Opus 5 (1M context) <noreply@anthropic.com>
2 files changed,
+2 insertions,
-2 deletions
| 42 |
42 |
|
# scaffolds from now on. 2.4.1 and 0.13.0 sat here once, and 2.5 and 0.28.0
|
| 43 |
43 |
|
# after that, while the suite reached 3.0.0 and 0.47.0.
|
| 44 |
44 |
|
makeover = "3.0"
|
| 45 |
|
- |
makeover-build = "0.49.0"
|
|
45 |
+ |
makeover-build = "0.51.0"
|
| 46 |
46 |
|
# The renderer's own scripts, written into `static/` beside the stylesheets.
|
| 47 |
47 |
|
# A build dependency and not a runtime one: this crate names no host, and
|
| 48 |
48 |
|
# reading three constants out of the webview renderer at build time does not
|
| 25 |
25 |
|
# resolves it to sixteen colours or to truecolor depending on what the terminal
|
| 26 |
26 |
|
# admits to.
|
| 27 |
27 |
|
makeover = "3.0"
|
| 28 |
|
- |
makeover-tui = { version = "0.33.0", features = ["theme"] }
|
|
28 |
+ |
makeover-tui = { version = "0.34.0", features = ["theme"] }
|