Second-Generation Managed Packaging Developer Guide
jNote: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Delete a Second-Generation Managed Package or Package Version
To delete a package or package version, users need the Delete Second-Generation Packages user permission. Before you delete a package, first delete all associated package versions.
| Package Type | Can I delete beta packages and package versions? | Can I delete released packages and package versions? |
|---|---|---|
| Second-Generation Managed Packages | Yes | No |
| Unlocked Packages | Yes | Yes |
Considerations for Deleting a Package or Package Version
- Deletion is permanent.
- Attempts to install a deleted package version will fail.
- Before deleting, ensure that the package or package version isn’t referenced as a dependency.
Examples:
1$ sf package delete -p "Your Package Alias"1$ sf package delete -p 0Ho...1$ sf package version delete -p "Your Package Version Alias"1$ sf package version delete -p 04t...These CLI commands can’t be used with first-generation managed packages or package versions. To delete a first-generation managed package, see View Package Details in the First-Generation Managed Packaging Developer Guide.