Skip to content

A treemap for finding and removing what fills your disk, for Omarchy. Rust + GPUI.

Rust

build: pin the toolchain so a fresh clone can't fail on a stale default

Aditya Gupta6a98a9ae393d
diff --git a/README.md b/README.md
index 7ee7533..8e75566 100644
--- a/README.md
+++ b/README.md
@@ -42,7 +42,9 @@ removes exactly what was installed.
You need Rust 1.97 or newer and a Wayland or X11 session with a GPU that GPUI
can drive (Vulkan). Distributions often package an older Rust;
-[rustup](https://rustup.rs) installs a current one.
+[rustup](https://rustup.rs) installs a current one. The repo pins 1.97 in
+`rust-toolchain.toml`, so with rustup the right toolchain is fetched on the
+first build even if `rustup default` points at something older.
### macOS
diff --git a/rust-toolchain.toml b/rust-toolchain.toml
new file mode 100644
index 0000000..39cd91b
--- /dev/null
+++ b/rust-toolchain.toml
@@ -0,0 +1,8 @@
+# The workspace's MSRV, pinned so rustup provisions it automatically: a fresh
+# clone builds on a machine whose default stable is older, instead of failing
+# with cargo's `rustc ... is not supported` before anything compiles. CI pins
+# the same version (see .github/workflows), and `make lint` needs clippy and
+# rustfmt, so they come with it.
+[toolchain]
+channel = "1.97"
+components = ["clippy", "rustfmt"]