package1 Commands | Salesforce CLI Command Reference

package1 version create

Create a first-generation package version in the release org.

Description for package1 version create

The package version is based on the contents of the specified metadata package. Omit --managed-released if you want to create an unmanaged package version.

Examples for package1 version create

Create a first-generation package version from the package with the specified ID and name the package version "example"; use your default org:

1sf package1 version create --package-id 033... --name example

Same as previous example, but provide a description and wait for 30 minutes for the package version to be created; use the specified org:

1sf package1 version create --package-id 033... --name example --description "example description" --wait 30 --target-org myorg@example.com

Flags

--json

Optional

Format output as json.

Type: boolean

--flags-dir FLAGS-DIR

Optional

Import flag values from a directory.

Type: option

-o | --target-org TARGET-ORG

Required

Username or alias of the target org. Not required if the `target-org` configuration variable is already set.

Type: option

--api-version API-VERSION

Optional

Override the api version used for api requests made by this command

Type: option

-i | --package-id PACKAGE-ID

Required

ID of the metadata package (starts with 033) of which you’re creating a new version.

Type: option

-n | --name NAME

Required

Package version name.

Type: option

-d | --description DESCRIPTION

Optional

Package version description.

Type: option

-v | --version VERSION

Optional

Package version in major.minor format, for example, 3.2.

Type: option

-m | --managed-released

Optional

Create a managed package version.

To create a beta version, don’t include this parameter.

Type: boolean

-r | --release-notes-url RELEASE-NOTES-URL

Optional

Release notes URL.

This link is displayed in the package installation UI to provide release notes for this package version to subscribers.

Type: option

-p | --post-install-url POST-INSTALL-URL

Optional

Post install URL.

The contents of the post-installation instructions URL are displayed in the UI after installation of the package version.

Type: option

-k | --installation-key INSTALLATION-KEY

Optional

Installation key for key-protected package (default: null).

Type: option

-w | --wait WAIT

Optional

Minutes to wait for the package version to be created (default: 2 minutes).

Type: option

Aliases for package1 version create

1force:package1:version:create

package1 version create get

Retrieve the status of a package version creation request.

Examples for package1 version create get

Get the status of the creation request for the package version with the specified ID in your default org:

1sf package1 version create get --request-id 0HD...

Same as previous example, but use the specified org:

1sf package1 version create get --request-id 0HD... --target-org myorg@example.com

Flags

--json: Optional; Format output as json.; Type: boolean
--flags-dir FLAGS-DIR: Optional; Import flag values from a directory.; Type: option
-o | --target-org TARGET-ORG: Required; Username or alias of the target org. Not required if the `target-org` configuration variable is already set.; Type: option
--api-version API-VERSION: Optional; Override the api version used for api requests made by this command; Type: option
-i | --request-id REQUEST-ID: Required; ID of the PackageUploadRequest (starts with 0HD).; Type: option

Aliases for package1 version create get

1force:package1:version:create:get

package1 version display

Display details about a first-generation package version.

Examples for package1 version display

Display details about the first-generation package version with the specified ID in your default org:

1sf package1 version display --package-version-id 04t...

Same as previous example, but use the specified org:

1sf package1 version display --package-version-id 04t... --target-org myorg@example.com

Flags

--json: Optional; Format output as json.; Type: boolean
--flags-dir FLAGS-DIR: Optional; Import flag values from a directory.; Type: option
-o | --target-org TARGET-ORG: Required; Username or alias of the target org. Not required if the `target-org` configuration variable is already set.; Type: option
--api-version API-VERSION: Optional; Override the api version used for api requests made by this command; Type: option
-i | --package-version-id PACKAGE-VERSION-ID: Required; ID (starts with 04t) of the metadata package version whose details you want to display.; Type: option

Aliases for package1 version display

1force:package1:version:display

package1 version list

List package versions for the specified first-generation package or for the org.

Examples for package1 version list

List all first-generation package versions in your default org:

1sf package1 version list

List package versions for the specified first-generation package in the specifief org:

1sf package1 version list --package-id 033... --target-org myorg@example.com

Flags

--json

Optional

Format output as json.

Type: boolean

--flags-dir FLAGS-DIR

Optional

Import flag values from a directory.

Type: option

-o | --target-org TARGET-ORG

Required

Username or alias of the target org. Not required if the `target-org` configuration variable is already set.

Type: option

--api-version API-VERSION

Optional

Override the api version used for api requests made by this command

Type: option

-i | --package-id PACKAGE-ID

Optional

Metadata package ID (starts with 033) whose package versions you want to list.

If not specified, shows all versions for all packages (managed and unmanaged) in the org.

Type: option

Aliases for package1 version list

1force:package1:version:list