First-Generation Managed Packaging Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Plan the Release of First-Generation Managed Packages
Remove Components from First-Generation Managed Packages
Delete Components from First-Generation Managed Packages
Modifying Custom Fields after a Package Is Released
Manage Versions of First-Generation Managed Packages
View Unused Components in a Managed Package
Push Package Upgrades to Subscribers
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Manage Versions of First-Generation Managed Packages

After you upload a package to AppExchange, you can still manage it from the Package Manager page.

User Permissions Needed
To upload packages: Upload AppExchange Packages

Building a new app? Have you considered using second-generation managed packages? Flexible versioning and the ability to share a namespace across packages are just two reasons why developers love creating second-generation managed packages. We think you’d love it, too. To learn more, see: Why Switch to Second-Generation Managed Packages, and Comparison of First- and Second-Generation Managed Packages.

Note

To manage your versions:

  1. From Setup, enter Packages in the Quick Find box, then select Packages.
  2. Select the package that contains the app or components you uploaded.
  3. Select the version number listed in the Versions tab.
    • To change the password option, click Change Password link.
    • To prevent new installations of this package while allowing existing installations to continue operating, click Deprecate.

      You can’t deprecate the most recent version of a managed package.

      Note

    • To make a deprecated version available for installation again, click Undeprecate.
    • To view the package installation URL, see Installation URL. Installation URLs contain the 04t package ID for the package version.