libgit2 / libgit2/libgit2sharp
Incompatibility with newer dotnet SDKs
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Why there's a lock into a specific dotnet cli version in the global.json ?
I think global.json could be improved adding roll forward (ref https://docs.microsoft.com/en-us/dotnet/core/tools/global-json?tabs=netcore3x#rollforward )
Reproduction steps
- Have lastest dotnet SDK - 3.1.301
- Try to build with dotnet core
- dotnet build
Expected behavior
- libgit2sharp builds
Actual behavior
- Get error message
- A compatible installed .NET Core SDK for global.json version [3.1.201] from [github/libgit2sharp/global.json] was not found
Version of LibGit2Sharp (release number or SHA1)
- 7fc4be5193dbdd08538b4b150332b5a73770e0f6
Operating system(s) tested; .NET runtime tested
- Ubuntu 18.04
- dotnet sdk 3.1.301
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the repository's global.json, which pins .NET Core SDK 3.1.201, and compare its settings with the documented roll-forward behavior. Reproduce the failure using dotnet SDK 3.1.301 and run dotnet build; done means the project builds with that newer SDK without the incompatible-version error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100