The Git source-code management system is preparing for the Git 2.56 release, expected around late September, currently in release-candidate form. This version includes over 700 non-merge commits with usability improvements but no fundamental changes. Notable additions include a `drop` subcommand for the experimental `git history` toolbox to remove commits, though it fails with merge commits. `git status` now suggests `git pull` for behind branches, and `git refs` gains `create`, `delete`, `update`, and `rename` subcommands. Other tweaks include `--delete-merged` for `git branch`, bisection protection, config lock retries, and `--resolved` for `git add`.

Looking ahead, maintainer Junio Hamano polled the community in early September on whether the next release should be the long-anticipated Git 3.0. This major version would introduce compatibility breaks, most significantly switching the default hash function from SHA-1 to SHA-256. While SHA-1 has known weaknesses, Git includes defenses against current attacks. The transition aims to secure repository integrity long-term, as hashes identify all objects and verify commit chains. The community must decide between finishing the year with 3.0 or issuing more 2.x releases first.