Develop Unlocked Packages

A package is a top-level container that holds important details about the app or package: the package name, description, and associated namespace.

You supply the package details in the package descriptor section of your sfdx-project.json project configuration file.

  • Create and Update an Unlocked Package

    When you’re ready to test or share your package, use the sf package create command to create a package.

  • Create New Versions of an Unlocked Package

    A package version is a fixed snapshot of the package contents and related metadata. The package version lets you manage changes and track what’s different each time you release or deploy a specific set of changes.

  • Guidance for Package Version Numbering

    Use package versions to evolve your managed package, and release subsequent package versions without breaking existing package users. Every package version is a fixed snapshot of the package contents and related metadata.

  • Code Coverage for Unlocked Packages

    Before you can promote and release an unlocked package, the Apex code must meet a minimum 75% code coverage requirement. You can install package versions that don’t meet code coverage requirements only in scratch orgs and sandboxes.

  • Considerations for Promoting Packages with Dependencies

    If your company is developing a package that has a package dependency, ask yourself these questions before promoting (releasing) a new package version.

  • Release an Unlocked Package

    Each new package version is marked as beta when its created. As you develop your package, you may create several package versions before you create a version that is ready to be released and installed in production orgs.

  • Update an Unlocked Package Version

    You can update most properties of a package version from the command line. For example, you can change the package version name or description. One important exception is that you can’t change the release status.

  • Hard-Deleted Components in Unlocked Packages

    When these components are removed from an unlocked package, they’re hard deleted from the target install org during the package upgrade.

  • Delete an Unlocked Package or Package Version

    Use the sf package version delete and sf package delete to delete packages and package versions that you no longer need.

  • View Package Details

    View the details of previously created packages and package versions from the command line.