Git LFS 2.4.0 released
A new version of Git LFS, the open source Git extension for versioning large files, is now available. Git LFS v2.4.0 comes with a rewrite of the underlying pattern matching…
A new version of Git LFS, the open source Git extension for versioning large files, is now available. Git LFS v2.4.0 comes with a rewrite of the underlying pattern matching engine, an enhanced API, standardized progress meter formatting, bug fixes, and more.
A new filepath-filter
With v2.4.0, you’ll get a complete reimplementation of the engine that decides which files do and don’t match commands that accept --include
and --exclude
flags. That means Git LFS has gained support for character ranges and classes. It’s also a step toward standardizing the meaning of certain patterns—stay tuned for more advanced pattern matching in future LFS releases.
Standardized progress meters
Many of the progress meters that have appeared throughout Git LFS are now unified into a single implementation, which matches Git’s style:
~/example (master) $ git lfs prune
prune: 13 local object(s), 3 retained" prune.log
prune: Deleting objects: 80% (8/10), done" prune.log
The progress meter you see when sending or receiving Git LFS objects is also clearer and more focused. You’ll now see a moving average rate for the transfer—and you’ll no longer see a count of “skipped” objects:
~/Desktop $ git lfs clone git@github.com:ttaylorr/example.git
Cloning into 'example'...
# ...
Downloading LFS objects: 40% (55/136), 96 MB | 15 MB/s
References in the API
Git LFS now includes any affected references in API requests. This change is a first step toward allowing contributions from owners in pull requests using Git LFS.
Additional updates
You’ll also see a handful of other new features and bug fixes in v2.4.0 like git lfs ls-files
, new flags in git lfs migrate
, more Linux support, and cleaned-up package internals.
And thanks to the great work of the Git LFS open source community, you’ll find support for NTLM SSPI authentication on Windows, fixes for memory alignment issues on 32-bit architectures, and more.
You can learn more about v2.4.0 in our release notes—and to see how Git LFS works with GitHub, check out our getting started guide.
Tags:
Written by
Related posts
Announcing GitHub Secure Open Source Fund: Help secure the open source ecosystem for everyone
Applications for the new GitHub Secure Open Source Fund are now open! Applications will be reviewed on a rolling basis until they close on January 7 at 11:59 pm PT. Programming and funding will begin in early 2025.
Software is a team sport: Building the future of software development together
Microsoft and GitHub are committed to empowering developers around the world to innovate, collaborate, and create solutions that’ll shape the next generation of technology.
Does GitHub Copilot improve code quality? Here’s what the data says
Findings in our latest study show that the quality of code written with GitHub Copilot is significantly more functional, readable, reliable, maintainable, and concise.