@salesforce/plugin-packaging/messages/package_convert.md

SF plugin that support Salesforce Packaging Platform

# summary

Convert a managed-released first-generation managed package into a second-generation managed package.

# description

The package conversion command automatically selects the latest released major.minor first-generation managed package version, and converts it into a second-generation managed package version.

Use --patch-version to specify a released patch version.

To retrieve details about a package version create request, including status and package version ID (04t), run "<%= config.bin %> package version create report -i 08c...".

To protect the contents of your package and to prevent unauthorized installation of your package, specify the --installation-key flag.

To promote a package version to released, you must use the --code-coverage parameter. The package must also meet the code coverage requirements.

To list package version creation requests in the org, run "<%= config.bin %> package version create list".

# examples

- Create a second-generation managed package version from the first-generation managed package with the specified ID and give it the installation key "password123"; uses your default Dev Hub org:

  <%= config.bin %> <%= command.id %> --package 033... --installation-key password123

- Similar to previous example, but uses the specified Dev Hub org:

  <%= config.bin %> <%= command.id %> --package 033... --installation-key password123 --target-dev-hub devhuborg@example.com

# flags.package.summary

ID (starts with 033) of the first-generation managed package to convert.

# flags.installation-key.summary

Installation key for key-protected package.

# flags.installation-key.description

Either an --installation-key value or the --installation-key-bypass flag is required.

# flags.installation-key-bypass.summary

Bypass the installation key requirement.

# flags.installation-key-bypass.description

If you bypass this requirement, anyone can install your package. Either an --installation-key value or the --installation-key-bypass flag is required.

# flags.definition-file.summary

Path to a definition file that contains features and org preferences that the metadata of the package version depends on.

# flags.definition-file.description

This definition file is similar to the scratch org definition file.

# flags.wait.summary

Minutes to wait for the package version to be created.

# flags.build-instance.summary

Instance where the conversion package version will be created, such as NA50.

# flags.verbose.summary

Display verbose command output.

# in-progress

Request in progress. Will wait a total of %s more seconds before timing out. Current Status='%s'.

# flags.seed-metadata.summary

Directory containing metadata to be deployed prior to conversion.

# flags.seed-metadata.description

The directory containing metadata that will be deployed on the build org prior to attempting package conversion.

# flags.patch-version.summary

Specific released patch version to be converted.

# flags.patch-version.description

Specify a released patch version as major.minor.patch to convert to a second-generation managed package version.

# flags.code-coverage.summary

Calculate and store the code coverage percentage by running the packaged Apex tests included in this package version.

# flags.code-coverage.description

Before you can promote and release a managed package version, the Apex code must meet a minimum 75% code coverage requirement.