version-control

Between August and October 2026, Cursor, GitHub and Anthropic described repository infrastructure designed around agent load; they differ on whether to keep Git, and the performance figures are self-reported.

Jujutsu 0.46.0, released October 7, can create Git worktrees alongside extra workspaces, raises the minimum Git version to 2.42.0 and lists seven breaking changes.

Git 2.56.0 adds git add --resolved and git branch --delete-merged, plus a merge-base change that cut a Linux kernel lookup from 0.29 to 0.01 seconds.

Git 2.56.0-rc1 adds new git refs subcommands and, via an amended 2.55 release note, confirms Rust will become a mandatory build dependency in Git 3.0.

Zed released a public beta of Delta, a collaboration tool built around AI-agent "threads" and a new DeltaDB versioning layer meant to replace GitHub pull requests.

GitHub Desktop 3.6.0, released June 26, brings a graphical worktree workflow and routes Copilot into commit messages and merge conflicts, with a model picker and BYOK.

Released June 29, the update extends the experimental git history command, adds inotify-based filesystem monitoring on Linux, and lets git push write to a group of remotes at once.

Jujutsu 0.42.0, released June 4, moves to the mimalloc allocator, drops several long-deprecated command options, and adds multi-revision support to jj show.

GitLab's next-generation source code management, shown at its Transcend event, keeps the Git protocol but rebuilds the backend so agents query repos server-side instead of cloning them.

Git 2.54, released April 20, introduces a new history-editing command inspired by Jujutsu, config-based hooks, geometric repacking by default, and a pluggable object database built over two years and roughly 400 commits.

Git 2.53 defaults Rust support in both build systems and unlocks geometric repacking for partial clones, setting the stage for a Git 3.0 release by late 2026.