Loading

Revert a 1GP and 2GP managed package to a beta version

Date de publication: Apr 7, 2026
Description

Once a managed package is uploaded as a released version, components in that version are locked and allow limited delete, edit, and remove options. 

With the release of the Component Deletion feature, depending on the component type, you may be able to delete the component to remove it from the package. If the component type is not supported by the Component Deletion feature, the only way it can be removed is by reverting the package version that introduced the component back to Beta.

Note:  2GP packages cannot be reverted to beta. Reverting to beta will not allow you to remove @deprecated from a managed class, nor can deprecated classes be removed when forced to beta. Also, reverting to beta will not allow deleted components to be undeleted.
With 2GP, it's not possible to revert a managed-released version to beta. As 2GP versions are not linear like 1GP packages, to make the desired modification to a managed 2GP version, you can branch from a previous version.
To learn more about branching from a previous version, please review Package Ancestors for Second-Generation Managed Packages. 

 

Résolution

If you need to remove a managed component that is not supported by the Component Deletion feature, please refer to the Help article below for details.

Easily Revert a Released First-Generation Managed Package Version to Beta

 

- Make sure the required (and subsequent) version(s) are not currently installed in any org. If they are, they will have to be uninstalled for us to revert back to beta (required to revert to beta).

- You are aware the new version will need to go through security review (only for Aloha-approved / AppExchange packages that have already passed).

- You may need to pay the review fee (only for Aloha-approved / AppExchange packages that have already paid).

 FAQs:

1. Why do I need to go through security review again? It's basically the same package.

We have no way of verifying the contents within the package without a security review. When in a Beta status, Partners have the ability to modify any of the unlocked code in the package, therefore security review is needed for the new version.

A. How long will it take?

The package will go through the normal review process of 6-8 weeks after a complete submission has been provided. Since the same reviewer usually handles re-tests/re-reviews of an app, turnaround is likely to be a bit quicker, but there is no guarantee.

Ensure you've provided *all* requirements when submitting the review as noted in the Security Review documentation, or this will delay the submission into the queue.
   
B. Do I need to pay again?

If a new version of a package is already paid for (i.e. under the same package ID # 033, but a different package version ID # 04t) you will have to complete the payment screen again but you will not be charged again ( it's just the way our wizard is set up).

* If restructuring the package with major changes (if it's essentially a new application), a coupon may not be approved and then you will have to pay. 

2. If we revert multiple versions (i.e. 1.0,1.1, and 1.2) what version number will the new version be once we upload a new managed version, post revert?

The new version will start with what the latest version was. In the above scenario, once a managed-released version is uploaded, it will be 1.2.

Numéro d’article de la base de connaissances

000381570

 
Chargement
Salesforce Help | Article