Publish Upgrades to First-Generation Managed Packages
User Permissions Needed | |
---|---|
To configure namespace settings: | Customize Application |
To create packages: | Create AppExchange Packages |
To upload packages: | Upload AppExchange Packages |
Any changes you make to the components in a managed package are automatically included in subsequent uploads of that package, with one exception. When you upgrade a package, changes to the API access are ignored even if the developer specified them. These changes are ignored so that the administrator installing the upgrade has full control. Installers must carefully examine the changes in package access in each upgrade during installation and note all acceptable changes. Then, because those changes are ignored, the admin must manually apply any acceptable changes after installing an upgrade.
- From Setup, enter Package Manager in the Quick Find box, then select Package Manager.
- Select the package from the list of available packages.
- View the list of package components. Changes you have made to components in this package are automatically included in this list. If the changes reference additional components, those components are automatically included as well. To add new components, click Add to add them to the package manually.
-
Click Upload and upload it as usual.
After you upload a new version of your Managed - Released package, you can click Deprecate so installers can’t install an older version. Deprecation prevents new installations of older versions without affecting existing installations.
You can’t deprecate the most recent version of a managed package upload.
- When you receive an email with the link to the upload on AppExchange, notify your installed users that the new version is ready. To distribute this information, use the list of installed users from the License Management Application (LMA). The License Management Application (LMA) automatically stores the version number that your installers have in their organizations.