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
{{ message }}
Repository navigation
Feature Request: Add "Support end date" metadata #13774
Packages that follow a set release lifecycle would expose this information. Then when building a package that claims to be supported longer than some of its transient dependencies NuGet would show a warning. This would help to proactively identify dependencies that would be deprecated before the using package.
Additional Context and Details
An extra feature would be to allow extending the "Support end date" without releasing a new package version or reuploading it.
I’m sure you are aware that nuget.org provides an option to deprecate packages. Customers will be notified if they have installed deprecated packages in the Visual Studio Package Manager UI and also via the dotnet list package --deprecated command in the CLI.
I’m sure you are aware that nuget.org provides an option to deprecate packages. Customers will be notified if they have installed deprecated packages in the Visual Studio Package Manager UI and also via the dotnet list package --deprecated command in the CLI.
Right, but there's currently no way of knowing through NuGet when the packages will be deprecated. This is important information to know when choosing dependencies as the latest version isn't the one that will be supported for longer for an STS release.
Due to lack of recent activity, this issue has been marked as a candidate for icebox cleanup. It will be closed if no further activity occurs within 14 more days. If the issue receives enough upvotes, it will be flagged with Triage:NeedsTriageDiscussion for team review.
Activity
kartheekp-ms commentedon Sep 7, 2024
I’m sure you are aware that nuget.org provides an option to deprecate packages. Customers will be notified if they have installed deprecated packages in the Visual Studio Package Manager UI and also via the
dotnet list package --deprecatedcommand in the CLI.AndriySvyryd commentedon Sep 7, 2024
Right, but there's currently no way of knowing through NuGet when the packages will be deprecated. This is important information to know when choosing dependencies as the latest version isn't the one that will be supported for longer for an STS release.
dotnet-policy-service commentedon Sep 28, 2026
Due to lack of recent activity, this issue has been marked as a candidate for icebox cleanup. It will be closed if no further activity occurs within 14 more days. If the issue receives enough upvotes, it will be flagged with
Triage:NeedsTriageDiscussionfor team review.AndriySvyryd commentedon Sep 28, 2026
This is still relevant