-
Notifications
You must be signed in to change notification settings - Fork 82
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
Microsoft.Web.LibraryManager.Cli & Microsoft.Web.LibraryManager.Build not updated #769
Comments
@phil-allen-msft sorry for spam, but what's status of Microsoft.Web.LibraryManager.Cli/ ? |
Sorry for bugspaming, but it's frustrating to contribute fix that I can't use :-) |
@leotsarev I'm not on the team anymore, just continuing to make contributions for the things I wish I could've done before. 😉 Unfortunately, I can't speed this along, but I'd like to see the new packages too. |
@jimmylewis sorry for spaming you then |
Sorry for confusion, I need Microsoft.Web.LibraryManager.Build, not Cli, but situation is the same |
For me, I´m wondering if Libman still supported outside Visual Studio (CLI & MSBuild task scenarios). It´s constantly breaking down in CI for me. I even contributed a fix, and half year later still I can´t get a working build in my hands. If it´s not supported, please make a official statement. |
Please update the packages on nuget.org. My fix was merged but no new packages have been pushed, yet. |
Describe the bug
https://www.nuget.org/packages/Microsoft.Web.LibraryManager.Cli/ not updated with latest changes. Particularly I interested in #753 because it haunting my builds for a long time
To Reproduce
https://www.nuget.org/packages/Microsoft.Web.LibraryManager.Cli/
is still 2.1.175 29a2892
A lot of changes in mainline happened.
Expected behavior
Release of latest version
Additional context
I'm happy to test some kind of beta nuget package.
The text was updated successfully, but these errors were encountered: