-
Notifications
You must be signed in to change notification settings - Fork 302
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
Add multi-targeting for .NET 8.0 and drop System.Collections.Specialized for .NET 6/8 #756
Comments
Hi @filipw, Thank you for raising this issue. This issue has been reviewed and added to our internal backlog for prioritisation . +1s and pull requests will help this move upward our backlog Issue for tracking : https://twilio-engineering.atlassian.net/browse/DII-1699 Thanks, |
Hi team, P.S it affects our prod build as security scans create errors messages. |
Hi, Also, this is not an enchantment, but a bug. The current library build doesn't dependents on that old package at all |
+1 please prioritize this issue. |
+1 |
Issue Summary
At the moment the library does not explicitly target .NET 8.0.
This means, that referencing it from a .NET 8.0 application means going over .NET Standard 2.1, which in turn pulls a ton of very old (dating back to 2016) dependencies via System.Collections.Specialized, some of which even have CVEs on them.
Taking this into account, and given that .NET 6.0 reaches end of life in November this year, it would be good to add .NET 8.0 to multi-targeting.
Additionally, the System.Collections.Specialized should also be dropped as explicit Nuget package reference for .NET 6.0 and .NET 8.0 as it's not needed there (the necessary types are already available).
Steps to Reproduce
<NuGetAuditMode>all</NuGetAuditMode>
dotnet publish -r linux-x64
Technical details:
The text was updated successfully, but these errors were encountered: