lee/bottom

mirror of https://github.com/ClementTsang/bottom.git synced 2026-07-08 05:30:47 +00:00

Files

T

Clement Tsang 40254c24e0 other: fix schema crate interfering with installs (#2109 )

This change should fix the issue around `cargo install` being confused by the schema generation binary by just moving it entirely into a separate tool "crate".

2026-06-27 17:44:44 -04:00

nightly

feature: add option to track unmounted disks on Linux (#2088 )

2026-06-20 04:19:32 +00:00

v0.9

…

v0.10

…

v0.11

other: run schema update (#1854 )

2025-11-06 23:26:15 +08:00

v0.12.0

uptick: 0.12.0 (#1915 )

2025-12-24 22:52:50 -05:00

v0.13.0

uptick: prep 0.13.0 update (#2089 )

2026-06-20 00:43:43 -04:00

v0.14.0

uptick: 0.14.0 (#2094 )

2026-06-20 09:03:19 +00:00

README.md

other: fix schema crate interfering with installs (#2109 )

2026-06-27 17:44:44 -04:00

README.md

Config JSON Schema

Generation

These are automatically generated from the code using schemars. The schemars derives are locked behind the generate_schema feature flag to avoid building unnecessary code for normal builds. Meanwhile, the generator itself lives in a separate tools/schema_gen helper crate. You can generate them like so:

# Will print out to stdout
cargo run --manifest-path tools/schema_gen/Cargo.toml

# e.g. for nightly
cargo run --manifest-path tools/schema_gen/Cargo.toml > schema/nightly/bottom.json

# e.g. for a specific version
cargo run --manifest-path tools/schema_gen/Cargo.toml -- 0.12.0 > schema/v0.12.0/bottom.json

Alternatively, run the scripts/schema/generate.sh script (for stable releases) or scripts/schema/nightly.sh (for nightly), which does all of this for you.

Publication

To publish these schemas:

Stable

Run scripts/schema/generate.sh <YOUR_VERSION>.
Make a PR and merge it.
Then, make a PR to schemastore to update the catalog. Here's an example of a PR.

Nightly

Run scripts/schema/nightly.sh.
Make a PR and merge it.