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
Copy file name to clipboardExpand all lines: docs/nuget-org/policies/deleting-packages.md
+15-1Lines changed: 15 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.topic: conceptual
11
11
12
12
nuget.org does not support permanent deletion of packages. Doing so would break every project depending on the availability of the package, especially with build workflows that involve package restore.
13
13
14
-
nuget.org does supports *unlisting* a package, which can be done in the package management page on the web site. Unlisted packages don't appear on nuget.org or in the Visual Studio UI, and do not appear in search results. Unlisted packages, however, can still be downloaded and installed by using an exact version number, which supports package restore. In addition, unlisted packages may still be discovered in the following specific scenarios:
14
+
nuget.org does supports [unlisting a package](#unlisting-a-package), which can be done in the package management page on the web site. Unlisted packages don't appear on nuget.org or in the Visual Studio UI, and do not appear in search results. Unlisted packages, however, can still be downloaded and installed by using an exact version number, which supports package restore. In addition, unlisted packages may still be discovered in the following specific scenarios:
15
15
16
16
- Package restore using floating versions (for example, `1.0.0-*`), if the latest available package matching the version or dependency constraints is an unlisted package.
17
17
- Replication of packages through the catalog (as the catalog also contains unlisted packages).
@@ -34,3 +34,17 @@ Packages that meet any of the following criteria are not allowed on the public N
34
34
If you find a package that is in violation of any of these items, click the **Report Abuse** link on the package details page and submit a report.
35
35
36
36
Note that the NuGet team and the .NET Foundation reserves the right to change these criteria at any time.
37
+
38
+
## Unlisting a package
39
+
Unlisting a package version hides it from search and from nuget.org package details page. This allows existing users of the package to continue using it but reduces new adoption since the package is not visible in search.
40
+
41
+
Steps to unlist a package:
42
+
43
+
1. Select `Your account name` (at the top right corner) >`Manage packages` > `Published packages`
44
+
1. Select the "Manage package" icon
45
+
1. Expand the "Listing" section and select the package version
46
+
1. Uncheck “List in search results” and select "Save"
47
+
48
+
The specific package version has now been unlisted. In order to verify this, logout of your account and navigate to the package page (without the version part) e.g.: https://www.nuget.org/packages/YOUR-PACKAGE-NAME/. You will see all versions of that package that have **not** been unlisted. However, the package owner, when logged in, can see all versions and their listing status.
49
+
50
+
It's also possible to deprecate a package version (in case you can't delete a package version). For more information about deprecating package versions, see [Deprecating packages](../deprecate-packages.md).
0 commit comments