You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: messages/package_convert.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,24 +1,22 @@
1
1
# summary
2
2
3
-
Create a second-generation package version from a first-generation package.
3
+
Convert a managed-released first-generation managed package into a second-generation managed package.
4
4
5
5
# description
6
6
7
-
The package convert creates a new package in the Dev Hub if one does not already exist for the specified first-generation package.
7
+
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.
8
8
9
-
It then creates a new package version in the Dev Hub with contents based on the specified first-generation package.
10
-
11
-
By default, the latest released non-patch version from the specified first-generation package will be converted. Use --patch-version to override the default. Read more about --patch-version option in help
9
+
Use --patch-version to specify a released patch version.
12
10
13
11
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...".
14
12
15
-
We recommend specifying the --installation-key to protect the contents of your package and to prevent unauthorized installation of your package.
13
+
To protect the contents of your package and to prevent unauthorized installation of your package, specify the --installation-key flag.
16
14
17
15
To list package version creation requests in the org, run "<%= config.bin %> package version create list".
18
16
19
17
# examples
20
18
21
-
- Create a second-generation package version from the first-generation package with the specified ID and give it the installation key "password123"; uses your default Dev Hub org:
19
+
- 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:
0 commit comments