Skip to content

Commit f416707

Browse files
authored
add package deprecation policy (dotnet#10346)
1 parent baa702b commit f416707

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

Documentation/policies/package-servicing.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,17 @@ The following libraries use this servicing model:
3737

3838
Users must be on the latest patch version of the package or a runtime-band to be supported.
3939

40+
## Package Deprecation
41+
42+
The .NET team uses [NuGet Package Deprecation](https://learn.microsoft.com/nuget/nuget-org/deprecate-packages) to indicate that a package or version is no longer supported. Deprecated packages remain available on nuget.org and can still be restored by projects.
43+
44+
.NET packages are marked deprecated when:
45+
46+
- The package version is associated with a .NET version that is out of support per the [.NET Support Policy](https://dotnet.microsoft.com/platform/support/policy).
47+
- The package was a preview or release candidate that has been superseded by a stable release.
48+
49+
Patch-to-patch updates within a supported version band will also be marked deprecated on a regular schedule following each servicing release. For example, when 8.0.2 ships, 8.0.1 will be deprecated in a subsequent update.
50+
4051
## Compatibility
4152

4253
Packages retain compatibility for supported .NET versions. A package will not drop support for a .NET version that is in support. When a .NET version goes out of support, packages released after that point may drop support for that .NET version.

0 commit comments

Comments
 (0)