1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
[]
= "dextui"
= "0.4.0"
= "2024"
= "A two-pane terminal UI for browsing and triaging dex tasks"
= "MIT"
= "https://github.com/DanielCarmingham/dextui"
# Same URL as `repository` for now, but it is not redundant: dist maps
# `homepage` and `description` into the generated Homebrew formula, and a
# formula with no homepage fails `brew audit`. Point it somewhere else the day
# there is somewhere else to point it.
= "https://github.com/DanielCarmingham/dextui"
= "README.md"
= ["tui", "tasks", "dex", "terminal", "ratatui"]
= ["command-line-utilities"]
# For people working *on* dextui, not people installing it. crates.io resolves
# the README's relative image links against `repository`, so the screenshots
# still render on the crate page without shipping 200 KB to every `cargo
# install`. The scripts are dev tooling and need the repo to be useful anyway.
# `.github/` and `dist-workspace.toml` are release plumbing: they describe how
# *this repo* builds and ships binaries, which is meaningless inside a crate
# tarball someone is about to compile themselves.
= [
"CLAUDE.md",
"docs/",
"scripts/",
".gitignore",
"handoff.md",
".claude/",
"AGENTS.md",
".github/",
"dist-workspace.toml",
]
# Edition 2024's own floor is 1.85, but ratatui 0.30.2 and tui-markdown 0.3.9 --
# the exact versions pinned above, not just some newer release -- both declare
# rust-version 1.88.0 themselves, which is the real floor. Understating it here
# does not relax anything; it only stops cargo from telling you why `cargo
# install` locked to it, right up until the day the actual build fails on an
# older toolchain instead. Bump this if a future dependency bump raises the
# floor again, in step with actually verifying it.
= "1.88"
# `cargo binstall dextui` does not find dist's artifacts on its own. Every one
# of binstall's default filename patterns contains the version
# (`{name}-{target}-v{version}`, `{name}_{version}_{target}`, and six more),
# and dist names its archives `{name}-{target}{suffix}` with the version only
# in the tag -- so the defaults miss every time and binstall silently falls
# back to a full source build, which looks like it worked and takes two
# minutes. binstall has no cargo-dist detection to lean on either: its repo
# mentions dist-manifest.json exactly once, in SIGNING.md.
#
# The layout below is dist's actual output, read out of a built archive rather
# than assumed -- note the leading `{name}-{target}/` directory, which is why
# `bin-dir` is not just `{ bin }`. Re-check it if dist's archive format ever
# changes; a wrong `bin-dir` here fails at extraction, not at download.
[]
= "{ repo }/releases/download/v{ version }/{ name }-{ target }{ archive-suffix }"
= "txz"
= "{ name }-{ target }/{ bin }{ binary-ext }"
[]
= "1.0.104"
= { = "0.4.45", = false, = ["clock"] }
= "0.29.0"
= "8.2.0"
= "0.30.2"
= { = "1.0.229", = ["derive"] }
= "1.0.151"
= "1.1.4"
= { = "0.3.9", = false }
# The profile that 'dist' will build with
[]
= "release"
= "thin"