Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update TFM's from .NET 5 to .NET 6 #11888

Open
dtivel opened this issue Jun 15, 2022 · 1 comment
Open

Update TFM's from .NET 5 to .NET 6 #11888

dtivel opened this issue Jun 15, 2022 · 1 comment
Labels
Functionality:SDK The NuGet client packages published to nuget.org Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:DCR Design Change Request

Comments

@dtivel
Copy link
Contributor

dtivel commented Jun 15, 2022

.NET 5 went out of support on May 10, 2022. We should update the NuGet.Client repo to target .NET 6 (LTS) instead of .NET 5.
@nkolev92 nkolev92 added Functionality:SDK The NuGet client packages published to nuget.org Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:DCR Design Change Request Pipeline:Icebox labels Jun 16, 2022
@nkolev92
Copy link
Member

Team Triage:

The target framework for class libraries sets the minimal API surface and is not impacted by the equivalent runtime support level.
The runtime is determined by the application that deploys these libraries instead.

That being said, we should probably move NuGet.Commandline.Xplat to net6.0, even if we don't move the libraries themselves.
We can ofc consider updating tfms for other reasons as well, such as needing new APIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Functionality:SDK The NuGet client packages published to nuget.org Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:DCR Design Change Request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nkolev92 @dtivel @jeffkl