Git 2.55-rc0 makes Rust the default in build system
Git just flipped Rust from opt-in to default in its build, a small switch that pushes one of the oldest dev tools closer to a Rust-normal future.
Git has stopped treating Rust like an add-on. In Git 2.55-rc0, the build system assumes Rust unless someone explicitly turns it off, and that shift makes the language look less like an experiment and more like part of the standard path through the project.
The change is practical before it is philosophical. In the Makefile, the old WITH_RUST switch has become NO_RUST, which means the default build now includes Rust unless a packager or contributor opts out. Meson follows the same idea: Rust stays enabled by default, but it can still be disabled for builds that need to stay non-Rust. That matters because Git is not a niche codebase. When a tool this central starts treating Rust as normal infrastructure, downstream distributions, CI setups, and contributor expectations all have to adjust.
Git 3.0 is the next obvious line in the sand. The plan is for Rust to become mandatory there, with no disable option at all. That makes 2.55-rc0 feel less like a random release-candidate tweak and more like the bridge between today’s configurable world and tomorrow’s Rust-required one. Work is also underway to make xdiff function with Rust, which is a stronger signal than a couple of helper modules or a wrapper library. xdiff sits close to the guts of Git’s diff machinery, so Rust is moving deeper into core code, not just standing at the edge.
The change also fits Git’s own long cadence for breaking transitions. The project’s BreakingChanges documentation says major breaking releases come irregularly, usually across multi-year spans. It points to Git 1.6.0 in August 2008 and Git 2.0 in May 2014 as past markers, and says the plan is to bump the major version again when the next breaking release lands. A 2025 Git mailing list discussion framed Rust in Git as a phased migration toward Git 3.0, with the first core patch series aimed at macOS and Linux while Windows was still blocked by build issues. That is the kind of slow, deliberate rollout Git has always favored.
The repository history backs that up. Rust source files are already in the tree, including src/varint.rs, so 2.55-rc0 did not introduce Rust from nowhere. It just made the language the default assumption in a project that has clearly been building toward this for a while.
This article was produced by Prism’s automated news system from verified source data, official records, and press releases, then run through automated quality and moderation checks before publishing. The system is built and supervised by the people who set the standards it runs under. Read our full AI policy.
Did this article answer your question?
