Bring the shop and alloy_tui pins up to date before an fw12 build
SHOP_REV was two commits behind shop's main, both documentation. The pin is
allowed to sit below the tip, but a build that is about to become the test
machine's install medium is exactly when it should be deliberate rather
than merely old. The new rev is the current ref tip on the remote, so the
guard above reports it as one instead of leaving it to cargo.
alloy_tui was written as 5.0.0 in both manifests while 5.0.1 is what cargo
has been resolving and building all along. Saying the version that is
actually used costs nothing and stops the manifest from being a stale
account of the tree.
- Co-Authored-By
- Claude Opus 5 (1M context) <noreply@anthropic.com>
3 files changed,
+3 insertions,
-3 deletions
| 94 |
94 |
|
# alone, so console edits — the thing that changes most often — reuse it
|
| 95 |
95 |
|
# instead of rebuilding a terminal that did not change. Moving it below the
|
| 96 |
96 |
|
# `COPY crates/` would defeat the dependency-cache split that follows.
|
| 97 |
|
- |
ARG SHOP_REV=53551eb50bbb0e9d0231b9063be93f0c820fdeb8
|
|
97 |
+ |
ARG SHOP_REV=03b0562a109f68c6e0f466d81abf1fe3c849f009
|
| 98 |
98 |
|
|
| 99 |
99 |
|
# Does the remote have anything to build from, before anything expensive runs.
|
| 100 |
100 |
|
#
|
| 13 |
13 |
|
path = "src/main.rs"
|
| 14 |
14 |
|
|
| 15 |
15 |
|
[dependencies]
|
| 16 |
|
- |
alloy_tui = "5.0.0"
|
|
16 |
+ |
alloy_tui = "5.0.1"
|
| 17 |
17 |
|
anyhow = "1"
|
| 18 |
18 |
|
clap = { version = "4", features = ["derive"] }
|
| 19 |
19 |
|
ratatui.workspace = true
|
| 13 |
13 |
|
path = "src/main.rs"
|
| 14 |
14 |
|
|
| 15 |
15 |
|
[dependencies]
|
| 16 |
|
- |
alloy_tui = "5.0.0"
|
|
16 |
+ |
alloy_tui = "5.0.1"
|
| 17 |
17 |
|
anyhow = "1"
|
| 18 |
18 |
|
clap = { version = "4", features = ["derive"] }
|
| 19 |
19 |
|
makeover.workspace = true
|