-
Notifications
You must be signed in to change notification settings - Fork 28
Pre-release versions of NuGet packages not updated #451
Comments
This issue is more than 3 months old by now and I still consider this a bug in the core functionality for C# projects, I hope you can get down to this soon guys. |
Looks like this is about fetching the |
Thank you a lot @greysteil! ❤️ |
@greysteil the bug is still here, I'm currently on Same happens with at least 7 other packages I use. |
In fact it didn't even update NLog 4.6.7 released 4 days ago, which is a stable release - link. Not sure what happened but it seems that no nuget packages are being updated at all right now. |
Should be fixed by dependabot/dependabot-core@dfff223, which I'll get deployed today. |
Thanks again ❤️ |
I can say this is not fixed as of today. I am talking about dotnet core projects where nuget.config files are not present at all. For stable versions it is working |
Hello.
Please refer to my
csproj
and the project here.I'm using several pre-release versions of NuGet packages, and to the best of my knowledge, dependabot is configured to automatically bump stable versions to newer stable releases, and pre-release versions to anything that is currently available.
I have at least 5 packages that are not being updated correctly, but to name one, Microsoft.Extensions.Logging.Configuration.
From my
csproj
:As we can see on the NuGet, the version that I'm using is a pre-release that is more than 3 months old, so there is no way of just a brief networking issue or anything, but wrong logic applied. The latest version (also pre-release) is
3.0.0-preview4.19216.2
as of today.Could you please take a look what is wrong and why dependabot doesn't update this package? It's not the only one that suffers from that, but I believe that solving this one will also solve all other ones. You have my project that you can fork and make tests on if you'd like to.
I don't have anything special in the dependabot config:
Thank you in advance for looking into this issue.
The text was updated successfully, but these errors were encountered: