VersionControlService 0.1.2
dotnet add package VersionControlService --version 0.1.2
NuGet\Install-Package VersionControlService -Version 0.1.2
<PackageReference Include="VersionControlService" Version="0.1.2" />
<PackageVersion Include="VersionControlService" Version="0.1.2" />
<PackageReference Include="VersionControlService" />
paket add VersionControlService --version 0.1.2
#r "nuget: VersionControlService, 0.1.2"
#:package VersionControlService@0.1.2
#addin nuget:?package=VersionControlService&version=0.1.2
#tool nuget:?package=VersionControlService&version=0.1.2
Provider-neutral version control workspace services for Fable and .NET consumers.
Learn more about Target Frameworks and .NET Standard.
-
net10.0
- VersionControlService.Abstractions (= 0.1.2)
- VersionControlService.Git (= 0.1.2)
- VersionControlService.LakeFs (= 0.1.2)
- VersionControlService.Runtime.Node (= 0.1.2)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Fixed
- The Git provider passes repository paths to git as literal pathspecs. Git used to read `[`, `]`, `*` and `?` in a file name as a pattern, so `Dematerialize` or `RestorePaths` on `runs/sample[1].csv` also reset uncommitted edits of `runs/sample1.csv`.
- When a file changes while `Dematerialize` frees it, the Git provider keeps the new content and the backup and fails with a message that names the backup path. The rollback used to delete whatever was at the path and put the older backup back. The failure has code `lfs_backup_retained` and `StateChanged = true`.
- `Materialize` downloads the file when `GIT_LFS_SKIP_SMUDGE=1` is set in the environment. The download of a single object used to get the pointer back and fail.
- After `Dematerialize`, the Git provider keeps the cached object when only an unpushed merge commit adds it, also when `log.diffMerges` is set in the git config. The check used to skip merge commits.