-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Drop support for out-of-support .NET versions #2798
Comments
As part of any breaking changes made when we do this, we should also consider removing any constructor overloads we've added over time to preserve binary compatibility which also ties into #2805. |
This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made. |
Will be resolved by #3007. |
Seems like you chose the phased approach based on that #3007 still contains .NET 6.0? |
Yes - see #3087. |
The published binaries and code are starting to get bloated with adding support for .NET 8 for #2792, so we should look to remove support for target frameworks that are now completely unsupported by Microsoft.
netcoreapp2.2
netcoreapp3.0
netcoreapp3.1
net5.0
net6.0
(from November 2024)net7.0
(from May 2024)This should be done as a major version bump.
We could either drop them all at once some time after November 2024, or do it in a phased approach:
The text was updated successfully, but these errors were encountered: