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

This article explains how to revert a released 1GP (first-generation) managed package version to beta in Salesforce when you need to remove a managed component that the Component Deletion feature does not support. It also answers common questions about security review, fees, and version numbering after a revert.

How to request a revert of a released managed package to beta

If you need to remove a managed component that is not supported by the Component Deletion feature, refer to the Help article Easily Revert a Released First-Generation Managed Package Version to Beta for details.

Requirements before you revert a managed package 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 about reverting a managed package to beta

Why do I need to go through security review again after reverting to beta?

It's basically the same package, but 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.

How long will the security review take after reverting to beta?

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.

Do I need to pay the security review fee again after reverting to beta?

If a new version of a package is already paid for (that is, under the same package ID number 033, but a different package version ID number 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 you are 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.

What version number will the new version have after reverting multiple versions?

If you revert multiple versions (for example 1.0, 1.1, and 1.2), the new version will start with what the latest version was. In that scenario, once a managed-released version is uploaded, it will be 1.2.