Convert a managed-released first-generation managed package into a second-generation managed package.
Description for package convert
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 "sf 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 "sf package version create list".
Aliases for package convert
force:package:convert
Flags
| Flag Name (Long) | Flag Name (Short) | Description |
|---|---|---|
| <code>‑‑api‑version</code> | N/A | Type: Value<br><br>Override the api version used for api requests made by this command |
| <code>‑‑code‑coverage</code> | <code>‑c</code> | Type: Boolean<br><br>Calculate and store the code coverage percentage by running the packaged Apex tests included in this package version.<br><br>Before you can promote and release a managed package version, the Apex code must meet a minimum 75% code coverage requirement. |
| <code>‑‑definition‑file</code> | <code>‑f</code> | Type: Value<br><br>Path to a definition file that contains features and org preferences that the metadata of the package version depends on.<br><br>This definition file is similar to the scratch org definition file. |
| <code>‑‑flags‑dir</code> | N/A | Type: Value<br><br>Import flag values from a directory. |
| <code>‑‑installation‑key</code> | <code>‑k</code> | Type: Value<br><br>Installation key for key-protected package.<br><br>Either an --installation-key value or the --installation-key-bypass flag is required. |
| <code>‑‑installation‑key‑bypass</code> | <code>‑x</code> | Type: Boolean<br><br>Bypass the installation key requirement.<br><br>If you bypass this requirement, anyone can install your package. Either an --installation-key value or the --installation-key-bypass flag is required. |
| <code>‑‑json</code> | N/A | Type: Boolean<br><br>Format output as json. |
| <code>‑‑package</code> | <code>‑p</code> | Type: Value<br>Required<br><br>ID (starts with 033) of the first-generation managed package to convert. |
| <code>‑‑patch‑version</code> | <code>‑a</code> | Type: Value<br><br>Specific released patch version to be converted.<br><br>Specify a released patch version as major.minor.patch to convert to a second-generation managed package version. |
| <code>‑‑seed‑metadata</code> | <code>‑m</code> | Type: Value<br><br>Directory containing metadata to be deployed prior to conversion.<br><br>The directory containing metadata that will be deployed on the build org prior to attempting package conversion. |
| <code>‑‑target‑dev‑hub</code> | <code>‑v</code> | Type: Value<br>Required<br><br>Username or alias of the Dev Hub org. Not required if the target-dev-hub configuration variable is already set. |
| <code>‑‑verbose</code> | N/A | Type: Boolean<br><br>Display verbose command output. |
| <code>‑‑wait</code> | <code>‑w</code> | Type: Value<br>Default value: 0 minutes<br><br>Minutes to wait for the package version to be created. |
Examples for package convert
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:
sf package convert --package 033... --installation-key password123
Similar to previous example, but uses the specified Dev Hub org:
sf package convert --package 033... --installation-key password123 --target-dev-hub devhuborg@example.com