First-Generation Managed Packaging Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Package Versions in First-Generation Managed Packages
- Major Release
- A major release denotes a Managed - Released package. During these releases, the major and minor numbers of a package version increase to a chosen value.
- Patch Release
- A patch release is only for patch versions of a package. During these releases, the patch number of a package version increments.
The following table shows a sequence of version numbers for a series of uploads:
| Upload Sequence | Type | Version Number | Notes |
|---|---|---|---|
| First upload | Managed - Beta | 1.0 | The firstManaged - Beta upload. |
| Second upload | Managed - Released | 1.0 | A Managed - Released upload. The version number doesn’t change. |
| Third upload | Managed - Released | 1.1 | Note the change of the minor release number for this Managed - Released upload. If you’re uploading a new patch version, you can't change the patch number. |
| Fourth upload | Managed - Beta | 2.0 | The first> Managed - Beta upload for version number 2.0. Note the major version number update. |
| Fifth upload | Managed - Released | 2.0 | A Managed - Released upload. The version number doesn’t change. |
When an existing subscriber installs a new package version, there’s still only one instance of each component in the package, but the components can emulate older versions. For example, a subscriber can use a managed package that contains an Apex class. If the publisher decides to deprecate a method in the Apex class and release a new package version, the subscriber still sees only one instance of the Apex class after installing the new version. However, this Apex class can still emulate the previous version for any code that references the deprecated method in the older version.
Package developers can use conditional logic in Apex classes and triggers to exhibit different behavior for different versions. Conditional logic lets the package developer support existing behavior in classes and triggers in previous package versions while evolving the code.
When you’re developing client applications using the API, you can specify the version of each package that you use in your integrations.