Update minimum required Git version checks #6028
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since commit a343a11 of PR #1461, a number of our commands, including
git lfs pull,git lfs push, andgit lfs track, have checked the version of the currently available Git program and reported an error if it was not at least version 1.8.2.However, when we added support for the
git lfs migratecommand in PR #2353, the actual minimum supported version of Git was changed from 1.8.x to 1.9.0 (in commit 1d0e834) and then to 2.0.0 (in commit 5aea841).These changes were made to the Travis CI configuration in use at the time, and later migrated to our current GitHub Actions CI workflow in commit c32820806229c3f42364d989f7a8597f73cb107ba of PR #3808. This workflow continues to run our Git LFS test suite using Git 2.0.0.
More recently, in commit 1501265 of PR #5921, we updated our
READMEfile to document that the current minimum supported version of Git we require is v2.0.0.We therefore now update the minimum Git version required by the Git LFS client to 2.0.0 by adjusting the version string defined in the
requireGitVersion()function of ourcommandspackage.