-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.5.0 is still not on nuget.org #1606
Comments
This allows us to ship 2.5.0 even if they haven't done so on nuget.org See git-ecosystem/git-credential-manager#1606
This allows us to ship 2.5.0 even if they haven't done so on nuget.org See git-ecosystem/git-credential-manager#1606 Fixes #88
This allows us to ship 2.5.0 even if they haven't done so on nuget.org See git-ecosystem/git-credential-manager#1606 Fixes #88
Is there a reason why this is still not on nuget? |
If you need to use it exclusively as a library from NS2.0, you can use Devlooped.CredentialManager which provides the portable v2.5.0 implementation. |
What I ended up doing was to modify the json file internally and and a {
"runtimeOptions": {
"tfm": "net7.0",
+ "rollForward":"Major",
"framework": {
"name": "Microsoft.NETCore.App",
"version": "7.0.13"
},
"configProperties": {
"System.Reflection.Metadata.MetadataUpdater.IsSupported": false
}
}
}
|
We are currently facing some issues publishing a correctly signed package to Nuget.org. Due to recent sponsorship/corporate funding priority changes, work on GCM has unfortunately slowed significantly. Please watch this space! |
In the meantime, can you at least add a note to the installation instructions not to use the dotnet tool method of installation until further notice? This is kind of a big deal, seems to me. Thanks! |
Hi is there any progress on releasing new GCM version 2.5.1 to dotnet tool? Currently 2.4.1 is the latest one. Thanks! |
Workaround using
|
Originally posted by @mjcheetham in #1702 (comment) |
See https://www.nuget.org/packages/git-credential-manager#versions-body-tab
The text was updated successfully, but these errors were encountered: