Git moves Rust to a default dependency
The release of Git 2.55 marks a significant shift in the project's build architecture, signaling a long-term transition toward safer memory management.
Adrian Volk
Jul 3, 2026 · 1 min read
Rust is no longer an experimental opt-in for the world's primary version control system. With the release of Git 2.55, the language is now enabled by default during the build process. While developers can still bypass the requirement with a specific flag, the shift clarifies the project's technical direction. Maintainers have indicated that Rust support may become mandatory in future major versions, likely starting with Git 3.0.
Beyond its architectural changes, the release introduces practical tooling for repository maintenance. A new experimental sub-command simplifies the correction of historical commits, allowing staged changes to be merged directly into older entries without the friction of an interactive rebase. These shifts in both language and logic reflect a broader institutional trend: hardening the core infrastructure of the software supply chain against legacy vulnerabilities.