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_pushupgrade_schedule.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,14 @@ The filename of the .csv file that contains the list of orgs that need the packa
35
35
36
36
Comma-separated list of subscriber org IDs that need the package upgrade.
37
37
38
+
# flags.migrate-to-2gp.summary
39
+
40
+
Indicates the push upgrade request is a migration from 1GP to 2GP.
41
+
42
+
# flags.migrate-to-2gp.description
43
+
44
+
Include this flag to specify that the push upgrade request represents a migration from a 1GP package to a 2GP package. The command must be run against the Dev Hub that owns the 2GP package.
45
+
38
46
# error.invalid-package-version
39
47
40
48
Invalid package version.
@@ -67,6 +75,9 @@ Either org list file or org list input must be supplied.
67
75
- Schedule a push upgrade that initiates as soon as possible:
Push upgrade has been scheduled. To check the status of this push upgrade, use push upgrade request ID [%s] with either “package push-upgrade list” or “package push-upgrade report”.
99
+
Push upgrade has been scheduled. To check the status of this push upgrade, use push upgrade request ID [%s] with either "package push-upgrade list" or "package push-upgrade report".
0 commit comments