What’s New in Git 2.55 and 3.0

What Git 2.55 and Git 3.0 Mean for Your Workflow

In late June 2026, the Git project shipped version 2.55 with contributions from over 100 contributors, 33 of them new, as documented in GitHub blog’s highlights post. A few weeks earlier, Git Rev News Edition 134 documented a major overhaul of the git log -L output pipeline. By the end of this year, Git 3.0 is expected to land with SHA-256 as the default hash algorithm, a mandatory Rust build dependency, and the reftable reference backend becoming the default for new repositories, per DeployHQ’s analysis of the project roadmap.

These changes directly affect how git log and git rev-parse behave in production. Our previous post on this topic covered the basics of filtering, formatting, and reference resolution. This article picks up where that one left off: what has changed in 2026, how the new features work, and what you need to update in your scripts and workflows.

git log -L Gets the Standard Diff Pipeline

The git log -L option has long been one of Git’s most underused features. It traces the evolution of a specific line range or function within a file. But for years, its diff output was generated by a hand-rolled helper called dump_diff_hacky() in line-log.c, with a NEEDSWORK comment admitting the approach was a placeholder.

That changed in early 2026. Developer Michael Montalbo submitted a four-patch series that routed the -L output through Git’s standard diff pipeline, as documented in Git Rev News Edition 134. The practical consequence: almost every diff formatting option that users rely on (--word-diff, --color-moved, the -w/-b whitespace options, --no-prefix, --full-index, --abbrev, and the pickaxe options -S/-G) was silently ignored when combined with -L.

As of Git 2.54 (shipped in April 2026, per LWN’s release coverage) and confirmed in Git 2.55, these options now work with -L. The hand-rolled output also omitted index lines, new file mode headers, and funcname context in @@ hunk headers. All of those are now present.

What this means for you:

Note: The following code is an illustrative example and has not been verified against official documentation. Please refer to the official docs for production-ready code.

# Before 2026: --word-diff was silently ignored with -L
git log -L 45,60:payment.go --word-diff
# After 2026: --word-diff actually works

# Before: -S pickaxe was ignored with -L
git log -L :validate_payment:payment.go -S "nullptr"
# After: pickaxe search works inside line-tracked history

# Before: no funcname context in @@ headers
# After: standard funcname context appears

This is not a minor cosmetic change. If you have ever tried to track down when a specific string appeared inside a specific function across a file’s history, you could not do that with a single command before 2026. Now you can. As Junio Hamano, Git’s maintainer, wrote in response to the patch series: “Exciting.”

One caveat: tools that parse -L output may need to handle additional lines (index lines, new file mode headers) that were previously absent. Non-patch diff formats (--raw, --numstat, --stat) remain unimplemented for -L as of Git 2.55, as noted in the patch series cover letter.

Git 2.55: New Features That Change How You Use git log and rev-parse

Git 2.55, released on June 29, 2026, introduced several features that directly affect how developers work with commit history and reference resolution. The release included work from over 100 contributors, 33 of them new.

–max-count-oldest for git log

Previously, getting the oldest N commits in a range required piping through --reverse | tail. Git 2.55 adds --max-count-oldest= to git log and git rev-list, returning the oldest commits directly:

# Before 2.55: two-step dance
git log --reverse --oneline | tail -5

# After 2.55: single command
git log --max-count-oldest=5 --oneline

This matters for scripts that need to find the earliest commits matching a filter. Combined with --since and --author, you can now write cleaner automation.

Tidier git log –graph with Lane Capping

The --graph option now supports lane capping. When a repository has many parallel branches, the ASCII graph can become unreadable. You can now cap the number of lanes, collapsing anything beyond the limit to ~:

git log --graph --oneline --decorate --graph-lanes=8

For monorepos with dozens of active feature branches, this keeps the graph readable without losing information.

git history fixup

This is the most impactful new porcelain command for day-to-day work. Instead of the three-step git add --fixup + git rebase -i --autosquash ritual, you can now stage a fix and fold it into an older commit in one step:

# Stage fix
git add -p
# Fold it into commit abc1234
git history fixup abc1234

The command keeps the original commit’s message and author, replays subsequent commits, and aborts cleanly on conflicts. This is the same mechanism as --fixup + --autosquash but without the interactive rebase editor.

git format-rev

Git 2.55 introduces git format-rev, a new builtin that pretty-formats revision expressions read from standard input. Instead of spawning a git log process per line of input, you can pipe commit hashes through a single invocation:

# Before: slow loop
while read hash; do
 git log --oneline -1 "$hash"
done /tmp/commits.txt

# Format them in one process
cat /tmp/commits.txt | git format-rev --pretty=format:"- %s (%h, %an)" --no-merges

# Output:
# - fix: resolve null pointer in payment processor (a3f2b1d, Maria Chen)
# - feat: add retry logic for webhook delivery (d4e5f6g, James Park)
# - docs: update API reference for v2 endpoints (h7i8j9k, Priya Singh)

This replaces the old pattern of looping over commits with individual git log calls, which was slow for large ranges.

Comparison Table: git log vs rev-parse vs rev-list vs reflog in 2026

The key distinction remains: git log shows a timeline of commits with rich filtering, git rev-parse resolves references to hashes without displaying any history, and git rev-list is the scripting-oriented backend that powers both. In 2026, the lines between git log and git rev-list have blurred further with shared options like --max-count-oldest.

Key Takeaways

• The git log -L option now supports --word-diff, --color-moved, whitespace options, and pickaxe search (-S/-G), all of which were silently ignored before 2026. This is the result of a patch series by Michael Montalbo, merged in Git 2.54.
• Git 2.55 introduced --max-count-oldest for git log and git rev-list, lane capping for --graph, git history fixup for one-step commit amending, and git format-rev for batch formatting of commit hashes.
• Git 3.0 (expected late 2026) makes SHA-256 the default hash for new repositories. Scripts that parse hashes by fixed length will break. Use git rev-parse --short instead of substring operations.
• Reftable becomes the default ref backend in Git 3.0. Scripts that read .git/refs/ directly will break. Migrate to git rev-parse and git for-each-ref.
• The git format-rev builtin replaces slow shell loops over commit hashes with a single process, reducing CI pipeline runtime for changelog generation.

Sources and References

Sources cited while researching and writing this article:

• documented in GitHub blog’s highlights post
• Git Rev News Edition 134 (April 30th, 2026) – git.github.io
• Git 3.0: Release Date, Features, and What Developers Need to Know
• LWN’s release coverage
• Git 2.55: the new features you will actually use · GitFlow
• git-scm docs