Skip to content

Commit 89b45cf

Browse files
authored
Remove /v7/ from link (evergreen🌲) (#281)
1 parent 39631af commit 89b45cf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/packages-and-modules/updating-and-managing-your-published-packages/unpublishing-packages-from-the-registry.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Unpublishing packages from the registry
33
---
44
import shared from '../../../src/shared.js'
55

6-
As a package owner or collaborator, if your package has no dependents, you can permanently remove it from the npm registry by using the CLI. You can [unpublish](https://docs.npmjs.com/cli/v7/commands/npm-unpublish) within 72 hours of the initial publish; beyond 72 hours, you can still unpublish your package if [it meets certain criteria](https://www.npmjs.com/policies/unpublish).
6+
As a package owner or collaborator, if your package has no dependents, you can permanently remove it from the npm registry by using the CLI. You can [unpublish](https://docs.npmjs.com/cli/commands/npm-unpublish) within 72 hours of the initial publish; beyond 72 hours, you can still unpublish your package if [it meets certain criteria](https://www.npmjs.com/policies/unpublish).
77

88
These criteria are set to avoid damaging the JavaScript package ecosystem. If you cannot unpublish your package, you can [deprecate it instead](/deprecating-and-undeprecating-packages-or-package-versions).
99

0 commit comments

Comments
 (0)