You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a packes.lock.json file in my project and thus can observe the changes to the dependency tree when updating packages, including changes to transitive dependencies. My project is on .NET 8. Updating LINQKit.Core from 1.2.5 to 1.2.6 leads to the diff against packages.lock.json below. I'm not sure for which recent CVEs
was added in eb4ba2b. But it seems to me that adding these dependencies even for the most recent target frameworks (because they are dependencies for the netstandard2.1 target) might be unfavorable for consumers on recent .NET versions that don't require System.Net.Http etc. from NuGet.
The text was updated successfully, but these errors were encountered:
StefH
changed the title
1.2.6 introduces a lot of legacy dependencies to modern consumers
LinqKit.Core 1.2.6 introduces a lot of legacy dependencies to modern consumers
Nov 18, 2024
For which reasons/CVEs were these dependencies added? E.g. System.Net.Http 4.3.4 is Last updated 10/9/2018 and thus adding it as a dependency probably doesn't help with more recent vulnerabilities, I think 🤔 - no matter which target framework it is added to.
I use a
packes.lock.json
file in my project and thus can observe the changes to the dependency tree when updating packages, including changes to transitive dependencies. My project is on .NET 8. Updating LINQKit.Core from 1.2.5 to 1.2.6 leads to the diff againstpackages.lock.json
below. I'm not sure for which recent CVEswas added in eb4ba2b. But it seems to me that adding these dependencies even for the most recent target frameworks (because they are dependencies for the netstandard2.1 target) might be unfavorable for consumers on recent .NET versions that don't require
System.Net.Http
etc. from NuGet.The text was updated successfully, but these errors were encountered: