No matches found
Try choosing different filters or resetting your filter selections.
Packaging: Unlocked Packages Generally Available
The generally available version has enhanced unlocked packages,
including support for patch version numbers, extracting package dependency information, moving
metadata between unlocked packages, and managing deprecated metadata.
-
Patch Version Numbers in Unlocked Packages Are Supported
You can now use patch version numbers for your unlocked package versions. Previously, patch numbers were not supported and always had to be 0. -
Extract Dependency Information for Unlocked Packages
For an installed unlocked package, you can now run a simple SOQL query to extract its dependency information. You can also create a script to automate the installation of unlocked packages with dependencies. -
More Metadata Components Are Hard-Deleted in Unlocked Packages
Many more metadata components are now hard-deleted from the target org when deleted from an unlocked package. -
Enable Migration of Deprecated Metadata in Unlocked Packages
As you start creating more unlocked packages, you might need to refactor your package and move metadata from one unlocked package to another unlocked package. You can now deprecate metadata in an unlocked package, move that metadata to a new package, and then install the new package in your production org. Upon successful installation of the new package, the deprecated metadata becomes associated with the new package. This feature simplifies that process. -
Lock Down Information During Installation of Installation-Key-Protected Unlocked Packages
We are making unlocked packages more secure with this change. An installation key is required as the first step during installation, ensuring that no package information is disclosed until the correct installation key is supplied. Previously, keys were verified only at the end of the package install. Moving verification to the start of the install protects package information, like the name and components, from users who don’t possess the key. -
Adopt Instanceless My Domain URL Best Practices
A critical update in Spring ’18 removed instance names from My Domain URLs. Update existing plug-in packages to support instanceless URLs before the critical update’s auto-activation date. Replace hard-coded references with relative URLs. Going forward, build packages that support both instance and instanceless URLs.