Skip to content

Releases: microsoft/VFSForGit

VFS For Git 1.0.19116.1

26 Apr 15:30
be3eb72
Compare
Choose a tag to compare
Pre-release

Update components included with internal distribution

VFS For Git 1.0.19113.4

24 Apr 13:32
be3eb72
Compare
Choose a tag to compare
Pre-release

Includes fixes to config settings for internal users only

VFS for Git 1.0.19101.1

22 Apr 13:10
be3eb72
Compare
Choose a tag to compare
Pre-release

Release notes:

  • Fixed several incorrect interactions with credentials
    • Now scopes credential.useHttpPath to just dev.azure.com hostname
    • Now erases credentials on authentication failure
    • Now approves credentials on authentication success
  • Lots of live-site improvements
    • Correlate trace2 stream with VFS for Git stream with the Git session ID.
    • Break down update placeholders timings so we can see where time is spend during checkout.
  • Many smaller bug fixes

VFS for Git 1.0.19074.1

03 Apr 18:48
e4e3733
Compare
Choose a tag to compare

Bug fixes:

  • Consume new GCM to fix git credential erase behavior
  • Properly reacquire credentials during nuget upgrader
  • Disable commit-graph verify for performance concerns

VFS for Git 1.0.19060.1

04 Mar 16:26
4b1db58
Compare
Choose a tag to compare
Pre-release

Bug fixes:

  • gvfs upgrade could fail if its background processes were launched in an existing enlistment.
  • git multi-pack-index verify would run slowly if the objects directory had more than 2048 packfiles.
  • Improve error message from gvfs upgrade if the Git installation could not be found.

VFS for Git 1.0.19052.1

22 Feb 20:26
445f1f3
Compare
Choose a tag to compare
Pre-release

New Features:

  • Upgrade supports NuGet feeds as a distribution source.
  • Post-index-change hook will help ensure consistency between Git and VFS for Git's reckoning of the state of the repository, and eliminate a class of bugs.
  • VFS for Git now supports anonymous access for public repositories.
  • gvfs prefetch learned how to take --files-list.

Performance and Reliability

  • "Sparse" push algorithm should improve performance of pushes where only a small cone of a repository is modified.
  • Multi-threaded index reads will improve load time of large .git/index
  • Built-in git rebase is on by default.
  • No-op gvfs prefetch --hydrate performance is dramatically improved
  • Commit-graph and multi-pack-index are validated after writing to eliminate corruption scenarios
  • Multiple mount process reliability bugs have been squashed.
  • VFS for Git will performance maintenance in the background. This release will pack loose objects in .gvfsCache into packfiles.

General Improvments

  • Log files now include UTC offset.
  • Other bug fixes

Please see the full change log.

VFS For Git 1.0.18297.1: Upgrade test

24 Oct 20:38
878a589
Compare
Choose a tag to compare

This release is identical to the previous. It was published to test upgrade.

VFS for Git 1.0.18289.1: Prompt to upgrade and checkout perf

17 Oct 15:13
878a589
Compare
Choose a tag to compare

New Features

  • VFS for Git will check the GitHub releases for the configured ring and prompt occasionally when running Git commands in a VFS for Git repository. To configure your ring, use the new gvfs config verb, like:
    gvfs config upgrade.ring ["fast", "slow", "none"]
    VFS for Git will check in the background for an available upgrade. If one is available, a message will be shown periodically to the user in the post-command hook to run gvfs upgrade to install the new version.
  • In the future, VFS for Git will automatically upgrade as new bits become available in the configured ring, eliminating the need to run gvfs upgrade to

Performance Improvements

  • Upgraded to Git 2.19. This version brings with it improvements to unpack_trees to speed up checkout, merge, reset, and rebase.
  • Improvements to compact and maintain the ModifiedPaths.dat database to help mitigate the problem of command perf degrading over time in an enlistment.

General Improvements

  • A couple of fixes for using VS Code on top of VFS for Git.
  • Other perf and reliability fixes.

VFS for Git 1.0.18234.1: Status caching and background prefetch

23 Aug 17:53
745f747
Compare
Choose a tag to compare

Performance Improvements:

  • VFS for Git will prefetch commits and trees from a cache server in the background on a schedule, to improve the speed of user-initiated fetches, pulls, and pushes
  • VFS for Git will pre-calculate status in the background in response to changes in the workdir, to improve the speed of user-initiated statuses.
    • Important note: The status cache will not be enabled until after the first reboot after this version of VFS for Git is installed. VFS for Git will still work as normal, but without the status cache feature.

General Improvements

  • Fixed a bug that would cause VFS for Git mount process to shut down if it receives out-of-order ProjFS callbacks.

GVFS 1.0.18183.1

03 Jul 16:09
Compare
Choose a tag to compare

General improvements:

  • We have improved how GVFS handles enlistments in junctions and mapped to a drive letter.
  • We have started porting parts of the product to .NET Standard.
  • Updated Git for a security issue.
  • Better errors around ProjFS installation issues.
  • Fix backoff on cache server size endpoint 404.
  • GVFS has a better icon.
  • Improved reliability of how the installer upgrades from non-inboxed to inboxed ProjFS.
  • Better recovery from a process that terminates without releasing the GVFS lock.
  • Gracefully handle a missing shared object cache pack directory.

Performance improvements:

  • We have moved MIDX computation to a post-fetch thread. This should save blocking time per prefetch that downloads a packfile from the cache server.
  • We have enabled the generation of the serialized commit graph in the post-fetch thread. This should provide across-the-board perf wins in any command that walks many commits.
  • Improved the memory usage during MIDX computation.
  • Further optimizations to GVFS's index parsing, saving time on commands that need to reproject (like checkout).
  • Use commit graph generation numbers during force push, saving time on force pushes.