First-Generation Managed Packaging Developer Guide
jWhy Switch to Second-Generation Managed Packaging?
Register a Namespace for a First-Generation Managed Package
Package Versions in First-Generation Managed Packages
Create and Upload Patches in First-Generation Managed Packages
Work with Patch Versions
Versioning Apex Code
Apex Deprecation Effects for Subscribers
Update Your First-Generation Managed Package
Your app is ready for an update. Learn how to fix small issues with patches and make
major changes with upgrades.
-
Package Versions in First-Generation Managed Packages
A package version is a number that identifies the set of components uploaded in a package. The version number has the format majorNumber.minorNumber.patchNumber (for example, 2.1.3). -
Create and Upload Patches in First-Generation Managed Packages
Patch versions are developed and maintained in a patch development org. -
Work with Patch Versions
A patch version enables a developer to change the functionality of existing components in a managed package. Subscribers experience no visible changes to the package. Patches are minor upgrades to a Managed - Released package and only used for fixing bugs or other errors. -
Versioning Apex Code
When subscribers install multiple versions of your package and write code that references Apex classes or triggers in your package, they must specify the version that they’re referencing. -
Apex Deprecation Effects for Subscribers
Explore how deprecation of an Apex method impacts subscribers that install your managed package.