{"id":40983028,"url":"https://github.com/salesforcecli/plugin-packaging","last_synced_at":"2026-05-31T09:00:51.966Z","repository":{"id":38241207,"uuid":"500844474","full_name":"salesforcecli/plugin-packaging","owner":"salesforcecli","description":null,"archived":false,"fork":false,"pushed_at":"2026-05-30T09:30:23.000Z","size":8331,"stargazers_count":19,"open_issues_count":4,"forks_count":12,"subscribers_count":9,"default_branch":"main","last_synced_at":"2026-05-30T11:16:13.294Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"TypeScript","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/salesforcecli.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE.txt","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2022-06-07T13:07:38.000Z","updated_at":"2026-05-30T09:28:29.000Z","dependencies_parsed_at":"2023-09-21T19:48:04.703Z","dependency_job_id":"65a75fbe-99ba-4526-acda-40908d3ccaee","html_url":"https://github.com/salesforcecli/plugin-packaging","commit_stats":{"total_commits":435,"total_committers":19,"mean_commits":"22.894736842105264","dds":0.7586206896551724,"last_synced_commit":"dc8935801c057778fa20e09b1d20c59741683030"},"previous_names":[],"tags_count":302,"template":false,"template_full_name":"salesforcecli/plugin-template","purl":"pkg:github/salesforcecli/plugin-packaging","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-packaging","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-packaging/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-packaging/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-packaging/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/salesforcecli","download_url":"https://codeload.github.com/salesforcecli/plugin-packaging/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-packaging/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":33725060,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-05-31T02:00:06.040Z","response_time":95,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-01-22T07:19:04.016Z","updated_at":"2026-05-31T09:00:51.949Z","avatar_url":"https://github.com/salesforcecli.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# plugin-packaging;\n\n[![NPM](https://img.shields.io/npm/v/@salesforce/plugin-packaging.svg?label=@salesforce/plugin-packaging)](https://www.npmjs.com/package/@salesforce/plugin-packaging) [![Downloads/week](https://img.shields.io/npm/dw/@salesforce/plugin-packaging.svg)](https://npmjs.org/package/@salesforce/plugin-packaging) [![License](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://opensource.org/license/apache-2-0)\n\n### This plugin provides the sf cli commands that support the Salesforce Packaging Platform.\n\n## Install\n\nThis plugin is bundled with the Salesforce CLI, so you typically don't need to install it. However, if you want to install a specific version of the plugin you can run:\n\n```bash\nsf plugins:install @salesforce/plugin-packaging@x.y.z\n```\n\n_NOTE: If you install a specific version of a bundled plugin you will not get an updated packaging plugin when the CLI updates. You must either update to the packaging plugin version you want manually, or uninstall the version of the plugin you have to go back to the CLI bundled version._\n\n## Issues\n\nPlease report any issues at https://github.com/forcedotcom/cli/issues\n\n## Contributing\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md)\n\n## Developing\n\nSee [DEVELOPING.md](DEVELOPING.md)\n\n## Commands\n\n\u003c!-- commands --\u003e\n\n- [`sf package convert`](#sf-package-convert)\n- [`sf package create`](#sf-package-create)\n- [`sf package delete`](#sf-package-delete)\n- [`sf package install`](#sf-package-install)\n- [`sf package install report`](#sf-package-install-report)\n- [`sf package installed list`](#sf-package-installed-list)\n- [`sf package list`](#sf-package-list)\n- [`sf package push-upgrade abort`](#sf-package-push-upgrade-abort)\n- [`sf package push-upgrade list`](#sf-package-push-upgrade-list)\n- [`sf package push-upgrade report`](#sf-package-push-upgrade-report)\n- [`sf package push-upgrade schedule`](#sf-package-push-upgrade-schedule)\n- [`sf package uninstall`](#sf-package-uninstall)\n- [`sf package uninstall report`](#sf-package-uninstall-report)\n- [`sf package update`](#sf-package-update)\n- [`sf package version create`](#sf-package-version-create)\n- [`sf package version create list`](#sf-package-version-create-list)\n- [`sf package version create report`](#sf-package-version-create-report)\n- [`sf package version delete`](#sf-package-version-delete)\n- [`sf package version displayancestry`](#sf-package-version-displayancestry)\n- [`sf package version displaydependencies`](#sf-package-version-displaydependencies)\n- [`sf package version list`](#sf-package-version-list)\n- [`sf package version promote`](#sf-package-version-promote)\n- [`sf package version report`](#sf-package-version-report)\n- [`sf package version retrieve`](#sf-package-version-retrieve)\n- [`sf package version update`](#sf-package-version-update)\n- [`sf package1 version create`](#sf-package1-version-create)\n- [`sf package1 version create get`](#sf-package1-version-create-get)\n- [`sf package1 version display`](#sf-package1-version-display)\n- [`sf package1 version list`](#sf-package1-version-list)\n\n## `sf package convert`\n\nConvert a managed-released first-generation managed package into a second-generation managed package.\n\n```\nUSAGE\n  $ sf package convert -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-k \u003cvalue\u003e] [-f\n    \u003cvalue\u003e] [-x] [-w \u003cvalue\u003e] [-m \u003cvalue\u003e] [--verbose] [-a \u003cvalue\u003e] [-c]\n\nFLAGS\n  -a, --patch-version=\u003cvalue\u003e     Specific released patch version to be converted.\n  -c, --code-coverage             Calculate and store the code coverage percentage by running the packaged Apex tests\n                                  included in this package version.\n  -f, --definition-file=\u003cvalue\u003e   Path to a definition file that contains features and org preferences that the metadata\n                                  of the package version depends on.\n  -k, --installation-key=\u003cvalue\u003e  Installation key for key-protected package.\n  -m, --seed-metadata=\u003cvalue\u003e     Directory containing metadata to be deployed prior to conversion.\n  -p, --package=\u003cvalue\u003e           (required) ID (starts with 033) of the first-generation managed package to convert.\n  -v, --target-dev-hub=\u003cvalue\u003e    (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                  configuration variable is already set.\n  -w, --wait=\u003cvalue\u003e              Minutes to wait for the package version to be created.\n  -x, --installation-key-bypass   Bypass the installation key requirement.\n      --api-version=\u003cvalue\u003e       Override the api version used for api requests made by this command\n      --verbose                   Display verbose command output.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Convert a managed-released first-generation managed package into a second-generation managed package.\n\n  The package conversion command automatically selects the latest released major.minor first-generation managed package\n  version, and converts it into a second-generation managed package version.\n\n  Use --patch-version to specify a released patch version.\n\n  To retrieve details about a package version create request, including status and package version ID (04t), run \"sf\n  package version create report -i 08c...\".\n\n  To protect the contents of your package and to prevent unauthorized installation of your package, specify the\n  --installation-key flag.\n\n  To promote a package version to released, you must use the --code-coverage parameter. The package must also meet the\n  code coverage requirements.\n\n  To list package version creation requests in the org, run \"sf package version create list\".\n\nALIASES\n  $ sf force package convert\n\nEXAMPLES\n  Create a second-generation managed package version from the first-generation managed package with the specified ID\n  and give it the installation key \"password123\"; uses your default Dev Hub org:\n\n    $ sf package convert --package 033... --installation-key password123\n\n  Similar to previous example, but uses the specified Dev Hub org:\n\n    $ sf package convert --package 033... --installation-key password123 --target-dev-hub devhuborg@example.com\n\nFLAG DESCRIPTIONS\n  -a, --patch-version=\u003cvalue\u003e  Specific released patch version to be converted.\n\n    Specify a released patch version as major.minor.patch to convert to a second-generation managed package version.\n\n  -c, --code-coverage\n\n    Calculate and store the code coverage percentage by running the packaged Apex tests included in this package\n    version.\n\n    Before you can promote and release a managed package version, the Apex code must meet a minimum 75% code coverage\n    requirement.\n\n  -f, --definition-file=\u003cvalue\u003e\n\n    Path to a definition file that contains features and org preferences that the metadata of the package version\n    depends on.\n\n    This definition file is similar to the scratch org definition file.\n\n  -k, --installation-key=\u003cvalue\u003e  Installation key for key-protected package.\n\n    Either an --installation-key value or the --installation-key-bypass flag is required.\n\n  -m, --seed-metadata=\u003cvalue\u003e  Directory containing metadata to be deployed prior to conversion.\n\n    The directory containing metadata that will be deployed on the build org prior to attempting package conversion.\n\n  -x, --installation-key-bypass  Bypass the installation key requirement.\n\n    If you bypass this requirement, anyone can install your package. Either an --installation-key value or the\n    --installation-key-bypass flag is required.\n```\n\n_See code: [src/commands/package/convert.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/convert.ts)_\n\n## `sf package create`\n\nCreate a package.\n\n```\nUSAGE\n  $ sf package create -v \u003cvalue\u003e -n \u003cvalue\u003e -t Managed|Unlocked -r \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e]\n    [--api-version \u003cvalue\u003e] [-d \u003cvalue\u003e] [-e] [--org-dependent] [-o \u003cvalue\u003e]\n\nFLAGS\n  -d, --description=\u003cvalue\u003e                  Description of the package.\n  -e, --no-namespace                         Create the package with no namespace; available only for unlocked packages.\n  -n, --name=\u003cvalue\u003e                         (required) Name of the package to create.\n  -o, --error-notification-username=\u003cvalue\u003e  Active Dev Hub user designated to receive email notifications for package\n                                             errors.\n  -r, --path=\u003cvalue\u003e                         (required) Path to directory that contains the contents of the package.\n  -t, --package-type=\u003coption\u003e                (required) Type of package.\n                                             \u003coptions: Managed|Unlocked\u003e\n  -v, --target-dev-hub=\u003cvalue\u003e               (required) Username or alias of the Dev Hub org. Not required if the\n                                             `target-dev-hub` configuration variable is already set.\n      --api-version=\u003cvalue\u003e                  Override the api version used for api requests made by this command\n      --org-dependent                        Depends on unpackaged metadata in the installation org; applies to unlocked\n                                             packages only.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Create a package.\n\n  First, use this command to create a package. Then create a package version.\n\n  If you don’t have a namespace defined in your sfdx-project.json file, use --no-namespace.\n\n  Your --name value must be unique within your namespace.\n\n  Run 'sf package list to list all packages in the Dev Hub org.\n\nALIASES\n  $ sf force package create\n\nEXAMPLES\n  Create an unlocked package from the files in the \"force-app\" directory; uses your default Dev Hub org:\n\n    $ sf package create --name MyUnlockedPackage --package-type Unlocked --path force-app\n\n  Create a managed packaged from the \"force-app\" directory files, give the package a description, and use the\n  specified Dev Hub org:\n\n    $ sf package create --name MyManagedPackage --description \"Your Package Descripton\" --package-type Managed \\\n      --path force-app --target-dev-hub devhub@example.com\n\nFLAG DESCRIPTIONS\n  -e, --no-namespace  Create the package with no namespace; available only for unlocked packages.\n\n    This flag is useful when you’re migrating an existing org to packages. But use a namespaced package for new\n    metadata.\n\n  -o, --error-notification-username=\u003cvalue\u003e\n\n    Active Dev Hub user designated to receive email notifications for package errors.\n\n    Email notifications include information about unhandled Apex exceptions, and install, upgrade, or uninstall failures\n    associated with your package.\n\n  -t, --package-type=Managed|Unlocked  Type of package.\n\n    The options for package type are Managed and Unlocked (Managed=DeveloperManagedSubscriberManaged,\n    Unlocked=DeveloperControlledSubscriberEditable). These options determine upgrade and editability rules.\n\n  --org-dependent  Depends on unpackaged metadata in the installation org; applies to unlocked packages only.\n\n    Use Source Tracking in Sandboxes to develop your org-dependent unlocked package. For more information, see \"Create\n    Org-Dependent Unlocked Packages\" in the Salesforce DX Developer Guide.\n```\n\n_See code: [src/commands/package/create.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/create.ts)_\n\n## `sf package delete`\n\nDelete a package.\n\n```\nUSAGE\n  $ sf package delete -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-n]\n\nFLAGS\n  -n, --no-prompt               Don't prompt before deleting the package.\n  -p, --package=\u003cvalue\u003e         (required) ID (starts with 0Ho) or alias of the package to delete.\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                configuration variable is already set.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Delete a package.\n\n  Specify the ID or alias of the package you want to delete.\n\n  Delete unlocked and second-generation managed packages. Before you delete a package, first delete all associated\n  package versions.\n\nALIASES\n  $ sf force package delete\n\nEXAMPLES\n  Delete a package using its alias from your default Dev Hub org:\n\n    $ sf package delete --package \"Your Package Alias\"\n\n  Delete a package using its ID from the specified Dev Hub org:\n\n    $ sf package delete --package 0Ho... --target-dev-hub devhub@example.com\n```\n\n_See code: [src/commands/package/delete.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/delete.ts)_\n\n## `sf package install`\n\nInstall or upgrade a version of a package in the target org.\n\n```\nUSAGE\n  $ sf package install -o \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-w \u003cvalue\u003e] [-k\n    \u003cvalue\u003e] [-b \u003cvalue\u003e] [-r] [-a all|package] [-s AllUsers|AdminsOnly] [-t DeprecateOnly|Mixed|Delete]\n\nFLAGS\n  -a, --apex-compile=\u003coption\u003e     [default: all] Compile all Apex in the org and package, or only Apex in the package;\n                                  unlocked packages only.\n                                  \u003coptions: all|package\u003e\n  -b, --publish-wait=\u003cvalue\u003e      Maximum number of minutes to wait for the Subscriber Package Version ID to become\n                                  available in the target org before canceling the install request.\n  -k, --installation-key=\u003cvalue\u003e  Installation key for key-protected package (default: null).\n  -o, --target-org=\u003cvalue\u003e        (required) Username or alias of the target org. Not required if the `target-org`\n                                  configuration variable is already set.\n  -p, --package=\u003cvalue\u003e           (required) ID (starts with 04t) or alias of the package version to install.\n  -r, --no-prompt                 Don't prompt for confirmation.\n  -s, --security-type=\u003coption\u003e    [default: AdminsOnly] Security access type for the installed package. Available\n                                  options are AdminsOnly and AllUsers.\n                                  \u003coptions: AllUsers|AdminsOnly\u003e\n  -t, --upgrade-type=\u003coption\u003e     [default: Mixed] Upgrade type for the package installation; available only for\n                                  unlocked packages.\n                                  \u003coptions: DeprecateOnly|Mixed|Delete\u003e\n  -w, --wait=\u003cvalue\u003e              Number of minutes to wait for installation status.\n      --api-version=\u003cvalue\u003e       Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Install or upgrade a version of a package in the target org.\n\n  To install or upgrade a package, specify a specific version of the package using the 04t package ID. The package and\n  the version you specified installs in your default target org unless you supply the username for a different target\n  org.\n\n  When upgrading an unlocked package, include the --upgrade-type value to specify whether any removed components are\n  deprecated or deleted. To delete components that can be safely deleted and deprecate the others, specify\n  \"--upgrade-type Mixed\" (the default). To deprecate all removed components, specify \"--upgrade-type DeprecateOnly\". To\n  delete all removed components, except for custom objects and custom fields, that don't have dependencies, specify\n  \"--upgrade-type Delete\". (Note: This option can result in the loss of data that is associated with the deleted\n  components.)\n\nALIASES\n  $ sf force package install\n\nEXAMPLES\n  Install or upgrade a package version with the specified ID in the org with username \"me@example.com\":\n\n    $ sf package install --package 04t... --target-org me@example.com\n\n  Install or upgrade a package version with the specified alias into your default org:\n\n    $ sf package install --package awesome_package_alias\n\n  Install or upgrade a package version with an alias that includes spaces into your default org:\n\n    $ sf package install --package \"Awesome Package Alias\"\n\n  Upgrade an unlocked package version with the specified ID and deprecate all removed components:\n\n    $ sf package install --package 04t... --upgrade-type DeprecateOnly\n\nFLAG DESCRIPTIONS\n  -a, --apex-compile=all|package\n\n    Compile all Apex in the org and package, or only Apex in the package; unlocked packages only.\n\n    Applies to unlocked packages only. Specifies whether to compile all Apex in the org and package, or only the Apex in\n    the package.\n\n    For package installs into production orgs, or any org that has Apex Compile on Deploy enabled, the platform compiles\n    all Apex in the org after the package install or upgrade operation completes.\n\n    This approach assures that package installs and upgrades don’t impact the performance of an org, and is done even if\n    --apex-compile package is specified.\n\n  -r, --no-prompt  Don't prompt for confirmation.\n\n    Allows the following without an explicit confirmation response: 1) Remote Site Settings and Content Security Policy\n    websites to send or receive data, and 2) --upgrade-type Delete to proceed.\n\n  -t, --upgrade-type=DeprecateOnly|Mixed|Delete\n\n    Upgrade type for the package installation; available only for unlocked packages.\n\n    For unlocked package upgrades, set this flag to one of these values:\n\n    - DeprecateOnly: Mark all removed components as deprecated.\n    - Mixed: Delete all removed components that can be safely deleted and deprecate the other components.\n    - Delete: Delete removed components, except for custom objects and custom fields, that don't have dependencies.\n```\n\n_See code: [src/commands/package/install.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/install.ts)_\n\n## `sf package install report`\n\nRetrieve the status of a package installation request.\n\n```\nUSAGE\n  $ sf package install report -o \u003cvalue\u003e -i \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -i, --request-id=\u003cvalue\u003e   (required) ID of the package install request you want to check; starts with 0Hf.\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nALIASES\n  $ sf force package install report\n\nEXAMPLES\n  Retrieve the status of a package installation request with the specified ID on your default org:\n\n    $ sf package install report --request-id 0Hf...\n\n  Similar to previous example, except use the org with username me@example.com:\n\n    $ sf package install report --request-id 0Hf... --target-org me@example.com\n```\n\n_See code: [src/commands/package/install/report.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/install/report.ts)_\n\n## `sf package installed list`\n\nList the org’s installed packages.\n\n```\nUSAGE\n  $ sf package installed list -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nALIASES\n  $ sf force package installed list\n\nEXAMPLES\n  List the installed packages in your default org:\n\n    $ sf package installed list\n\n  List the installed packages in the org with username me@example.com:\n\n    $ sf package installed list --target-org me@example.com\n```\n\n_See code: [src/commands/package/installed/list.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/installed/list.ts)_\n\n## `sf package list`\n\nList all packages in the Dev Hub org.\n\n```\nUSAGE\n  $ sf package list -v \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--verbose]\n\nFLAGS\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                configuration variable is already set.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n      --verbose                 Display extended package detail.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  List all packages in the Dev Hub org.\n\n  Description\n\nALIASES\n  $ sf force package list\n\nEXAMPLES\n  List all packages in the specified Dev Hub org:\n\n    $ sf package list --target-dev-hub devhub@example.com\n\n  List all packages details in the specified Dev Hub org, and show extended details about each package:\n\n    $ sf package list --target-dev-hub devhub@example.com --verbose\n```\n\n_See code: [src/commands/package/list.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/list.ts)_\n\n## `sf package push-upgrade abort`\n\nAbort a package push upgrade that has been scheduled. Only push upgrade requests with a status of Created or Pending can be aborted.\n\n```\nUSAGE\n  $ sf package push-upgrade abort -v \u003cvalue\u003e -i \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -i, --push-request-id=\u003cvalue\u003e  (required) ID of the package push request (starts with 0DV). This ID is returned after\n                                 the package push-upgrade schedule command completes successfully.\n  -v, --target-dev-hub=\u003cvalue\u003e   (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                 configuration variable is already set.\n      --api-version=\u003cvalue\u003e      Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Abort a package push upgrade that has been scheduled. Only push upgrade requests with a status of Created or Pending\n  can be aborted.\n\n  Specify the request ID that you want to abort. If applicable, the command displays errors related to the request.\n\n  To show all requests in the org, run \"sf package pushupgrade list --package 033...\".\n\nEXAMPLES\n  Cancel the specified package push upgrade request with the specified ID; uses your default Dev Hub org:\n\n    $ sf package push-upgrade abort --push-request-id 0DV...\n\n  Cancel the specified package push upgrade request in the Dev Hub org with username devhub@example.com:\n\n    $ sf package push-upgrade abort --push-request-id 0DV... --target-dev-hub devhub@example.com\n```\n\n_See code: [src/commands/package/push-upgrade/abort.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/push-upgrade/abort.ts)_\n\n## `sf package push-upgrade list`\n\nLists the status of push upgrade requests for a given package.\n\n```\nUSAGE\n  $ sf package push-upgrade list -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-l \u003cvalue\u003e] [-s\n    Created|Cancelled|Pending|In Progress|Failed|Succeeded] [--show-push-migrations-only]\n\nFLAGS\n  -l, --scheduled-last-days=\u003cvalue\u003e  Number of days in the past for which to display the list of push upgrade requests\n                                     that were scheduled. Used to filter the list output to only recently scheduled push\n                                     upgrades.\n  -p, --package=\u003cvalue\u003e              (required) Package ID (starts with 033) of the package that you want push upgrade\n                                     information for.\n  -s, --status=\u003coption\u003e              Status used to filter the list output Valid values are: Created, Canceled, Pending,\n                                     In Progress, Failed, or Succeeded\n                                     \u003coptions: Created|Cancelled|Pending|In Progress|Failed|Succeeded\u003e\n  -v, --target-dev-hub=\u003cvalue\u003e       (required) Username or alias of the Dev Hub org. Not required if the\n                                     `target-dev-hub` configuration variable is already set.\n      --api-version=\u003cvalue\u003e          Override the api version used for api requests made by this command\n      --show-push-migrations-only    Display only push upgrade requests for package migrations.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Lists the status of push upgrade requests for a given package.\n\n  Shows the details of each request to create a push upgrade in the Dev Hub org.\n\n  All filter parameters are applied using the AND logical operator (not OR).\n\n  To get information about a specific request, run \"sf package pushupgrade report\" and supply the request ID.\n\nALIASES\n  $ sf force package push-upgrade list\n\nEXAMPLES\n  List all package push upgrade requests in the specified Dev Hub org:\n\n    $ sf package push-upgrade list --package 033xyz --target-dev-hub myHub\n\n  List all package push upgrade requests in the specified Dev Hub org scheduled in the last 30 days:\n\n    $ sf package push-upgrade list --package 033xyz --scheduled-last-days 30 --target-dev-hub myHub\n\n  List all package push upgrade with a status Succeeded:\n\n    $ sf package push-upgrade list --package 033xyz –-status Succeeded\n\n  List all package push upgrade with a status Failed:\n\n    $ sf package push-upgrade list --package 033xyz –-status Failed\n```\n\n_See code: [src/commands/package/push-upgrade/list.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/push-upgrade/list.ts)_\n\n## `sf package push-upgrade report`\n\nRetrieve the status of a package push upgrade.\n\n```\nUSAGE\n  $ sf package push-upgrade report -v \u003cvalue\u003e -i \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -i, --push-request-id=\u003cvalue\u003e  (required) ID of the package push request (starts with 0DV). This ID is returned after\n                                 the package push-upgrade schedule command completes successfully.\n  -v, --target-dev-hub=\u003cvalue\u003e   (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                 configuration variable is already set.\n      --api-version=\u003cvalue\u003e      Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Retrieve the status of a package push upgrade.\n\n  Specify the request ID for which you want to view details. If applicable, the command displays errors related to the\n  request.\n\n  To show all requests in the org, run \"sf package pushupgrade list\".\n\nALIASES\n  $ sf force package push-upgrade report\n\nEXAMPLES\n  Retrieve details about the package push upgrade with the specified ID; uses your default Dev Hub org:\n\n    $ sf package push-upgrade report --push-request-id 0DV...\n\n  Retrieve details about the specified package push request in the Dev Hub org with username devhub@example.com:\n\n    $ sf package push-upgrade report --push-request-id 0DV... --target-dev-hub devhub@example.com\n```\n\n_See code: [src/commands/package/push-upgrade/report.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/push-upgrade/report.ts)_\n\n## `sf package push-upgrade schedule`\n\nSchedule a package push upgrade.\n\n```\nUSAGE\n  $ sf package push-upgrade schedule -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-t \u003cvalue\u003e] [-l\n    \u003cvalue\u003e | -f \u003cvalue\u003e] [--migrate-to-2gp]\n\nFLAGS\n  -f, --org-file=\u003cvalue\u003e        Filename of the CSV file that contains the list of subscriber org IDs that need the\n                                package upgrade. Either --org-list or --org-file must be specified.\n  -l, --org-list=\u003cvalue\u003e        Comma-separated list of subscriber org IDs that need the package upgrade. Either\n                                --org-list or --org-file must be specified.\n  -p, --package=\u003cvalue\u003e         (required) ID (starts with 04t) of the package version that the package is being\n                                upgraded to. The package version must be an active, non-beta package version.\n  -t, --start-time=\u003cvalue\u003e      Date and time (UTC) when the push upgrade is processed. Set to the earliest time that\n                                you want Salesforce to attempt to start the upgrade.\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org that owns the package.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n      --migrate-to-2gp          Upgrade from a first-generation managed package (1GP) to a second-generation managed\n                                package (2GP). Required when you’re pushing a 2GP package to orgs with the 1GP version\n                                installed.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Schedule a package push upgrade.\n\n  Represents a push upgrade request for upgrading a package in one or many orgs from one version to another version.\n  To initiate a push upgrade for an unlocked or second-generation managed package, the Create and Update\n  Second-Generation Packages user permission is required.\n  For second-generation managed packages, the push upgrade feature is available only for packages that have passed\n  AppExchange security review. To enable push upgrades for your managed package, log a support case in the Salesforce\n  Partner Community.\n  For unlocked packages, push upgrades are enabled by default.\n\n  Use the -–migrate-to-2GP flag to indicate you’re installing a converted second-generation managed package into an org\n  that has the first-generation managed package version of that package installed.\n\nEXAMPLES\n  Schedule a push upgrade that initiates at a specified time:\n\n    $ sf package push-upgrade schedule --package 04txyz --start-time \"2024-12-06T21:00:00\" --org-file \\\n      upgrade-orgs.csv --target-dev-hub myHub\n\n  Schedule a push upgrade that initiates as soon as possible:\n\n    $ sf package push-upgrade schedule --package 04txyz --org-file upgrade-orgs.csv --target-dev-hub myHub\n\n  Schedule a push migration from a 1GP package to a 2GP package:\n\n    $ sf package push-upgrade schedule --migrate-to-2gp --package 04txyz --start-time \"2024-12-06T21:00:00\" \\\n      --org-file upgrade-orgs.csv --target-dev-hub myHub\n\nFLAG DESCRIPTIONS\n  -f, --org-file=\u003cvalue\u003e\n\n    Filename of the CSV file that contains the list of subscriber org IDs that need the package upgrade. Either\n    --org-list or --org-file must be specified.\n\n    The file must contain one org per line. The org ID must be the only value in each row.\n    All listed orgs must have a package version installed in their org that is lower than the package version you\n    specified for the --package flag.\n\n  -t, --start-time=\u003cvalue\u003e\n\n    Date and time (UTC) when the push upgrade is processed. Set to the earliest time that you want Salesforce to attempt\n    to start the upgrade.\n\n    Scheduled push upgrades begin as soon as resources are available on the Salesforce instance, which is either at or\n    after the start time you specify. In certain scenarios, the push upgrade starts a few hours after the scheduled\n    start time.\n\n    As a best practice, schedule push upgrades at off-peak hours like 1:00 AM Saturday.\n    If you don't specify this flag, the push upgrade is scheduled to run as soon as resources are available on the\n    Salesforce instance.\n\n  -v, --target-dev-hub=\u003cvalue\u003e  Username or alias of the Dev Hub org that owns the package.\n\n    Overrides the value of the target-dev-hub configuration variable, if set.\n```\n\n_See code: [src/commands/package/push-upgrade/schedule.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/push-upgrade/schedule.ts)_\n\n## `sf package uninstall`\n\nUninstall a second-generation package from the target org.\n\n```\nUSAGE\n  $ sf package uninstall -o \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-w \u003cvalue\u003e]\n\nFLAGS\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n  -p, --package=\u003cvalue\u003e      (required) ID (starts with 04t) or alias of the package version to uninstall.\n  -w, --wait=\u003cvalue\u003e         Number of minutes to wait for uninstall status.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Uninstall a second-generation package from the target org.\n\n  Specify the package ID for a second-generation package.\n\n  To list the org’s installed packages, run \"sf package installed list\".\n\n  To uninstall a first-generation package, from Setup, enter Installed Packages in the Quick Find box, then select\n  Installed Packages.\n\nALIASES\n  $ sf force package uninstall\n\nEXAMPLES\n  Uninstall a package with specified ID from an org with username me@example.com:\n\n    $ sf package uninstall --package 04t... --target-org me@example.com\n\n  Uninstall a package with the specified alias from your default org:\n\n    $ sf package uninstall --package undesirable_package_alias\n\n  Uninstall a package with an alias that contains spaces from your default org:\n\n    $ sf package uninstall --package \"Undesirable Package Alias\"\n```\n\n_See code: [src/commands/package/uninstall.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/uninstall.ts)_\n\n## `sf package uninstall report`\n\nRetrieve the status of a package uninstall request.\n\n```\nUSAGE\n  $ sf package uninstall report -o \u003cvalue\u003e -i \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -i, --request-id=\u003cvalue\u003e   (required) ID of the package uninstall request you want to check; starts with 06y.\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nALIASES\n  $ sf force package uninstall report\n\nEXAMPLES\n  Retrieve the status of a package uninstall in your default org using the specified request ID:\n\n    $ sf package uninstall report --request-id 06y...\n\n  Similar to previous example, but use the org with username me@example.com:\n\n    $ sf package uninstall report --request-id 06y... --target-org me@example.com\n```\n\n_See code: [src/commands/package/uninstall/report.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/uninstall/report.ts)_\n\n## `sf package update`\n\nUpdate package details.\n\n```\nUSAGE\n  $ sf package update -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-n \u003cvalue\u003e] [-d\n    \u003cvalue\u003e] [-o \u003cvalue\u003e] [--enable-app-analytics] [-r \u003cvalue\u003e] [--skip-ancestor-check]\n\nFLAGS\n  -d, --description=\u003cvalue\u003e                  New description of the package.\n  -n, --name=\u003cvalue\u003e                         New name of the package.\n  -o, --error-notification-username=\u003cvalue\u003e  Active Dev Hub user designated to receive email notifications for package\n                                             errors.\n  -p, --package=\u003cvalue\u003e                      (required) ID (starts with 0Ho) or alias of the package to update.\n  -r, --recommended-version-id=\u003cvalue\u003e       ID of the package version that's installed when subscribers click the\n                                             Upgrade to Recommended Version option on the Installed Packages page of\n                                             their org.\n  -v, --target-dev-hub=\u003cvalue\u003e               (required) Username or alias of the Dev Hub org. Not required if the\n                                             `target-dev-hub` configuration variable is already set.\n      --api-version=\u003cvalue\u003e                  Override the api version used for api requests made by this command\n      --[no-]enable-app-analytics            Enable AppExchange App Analytics usage data collection on this managed\n                                             package and its components.\n      --skip-ancestor-check                  Bypass the ancestry check for setting a recommended version.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Update package details.\n\n  Specify a new value for each option you want to update.\n\n  Run \"sf package list\" to list all packages in the Dev Hub org.\n\nALIASES\n  $ sf force package update\n\nEXAMPLES\n  Update the name of the package with the specified alias; uses your default Dev Hub org:\n\n    $ sf package update --package \"Your Package Alias\" --name \"New Package Name\"\n\n  Update the description of the package with the specified ID; uses the specified Dev Hub org:\n\n    $ sf package update --package 0Ho... --description \"New Package Description\" --target-dev-hub devhub@example.com\n\nFLAG DESCRIPTIONS\n  -o, --error-notification-username=\u003cvalue\u003e\n\n    Active Dev Hub user designated to receive email notifications for package errors.\n\n    Email notifications include information about unhandled Apex exceptions, and install, upgrade, or uninstall failures\n    associated with your package.\n\n  -r, --recommended-version-id=\u003cvalue\u003e\n\n    ID of the package version that's installed when subscribers click the Upgrade to Recommended Version option on the\n    Installed Packages page of their org.\n\n    Specify the recommended package version for subscribers to install. If a subscriber has a package version installed\n    in their org that's lower than the version you set, the subscriber sees the Upgrade to Recommended Version option on\n    the Installed Packages page. Only released package versions can be set as the recommended version.\n```\n\n_See code: [src/commands/package/update.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/update.ts)_\n\n## `sf package version create`\n\nCreate a package version in the Dev Hub org.\n\n```\nUSAGE\n  $ sf package version create -v \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-b \u003cvalue\u003e] [-c |\n    --skip-validation] [-f \u003cvalue\u003e] [-k \u003cvalue\u003e] [-x] [-p \u003cvalue\u003e] [-d \u003cvalue\u003e] [--post-install-script \u003cvalue\u003e]\n    [--post-install-url \u003cvalue\u003e] [--releasenotes-url \u003cvalue\u003e] [--skip-ancestor-check] [--async-validation | ]\n    [--generate-pkg-zip] [-t \u003cvalue\u003e] [--uninstall-script \u003cvalue\u003e] [-e \u003cvalue\u003e] [-a \u003cvalue\u003e] [-n \u003cvalue\u003e] [-w \u003cvalue\u003e]\n    [--language \u003cvalue\u003e] [--verbose]\n\nFLAGS\n  -a, --version-name=\u003cvalue\u003e         Name of the package version to be created; overrides the sfdx-project.json value.\n  -b, --branch=\u003cvalue\u003e               Name of the branch in your source control system that the package version is based\n                                     on.\n  -c, --code-coverage                Calculate and store the code coverage percentage by running the packaged Apex tests\n                                     included in this package version.\n  -d, --path=\u003cvalue\u003e                 Path to the directory that contains the contents of the package.\n  -e, --version-description=\u003cvalue\u003e  Description of the package version to be created; overrides the sfdx-project.json\n                                     value.\n  -f, --definition-file=\u003cvalue\u003e      Path to a definition file similar to scratch org definition file that contains the\n                                     list of features and org preferences that the metadata of the package version\n                                     depends on.\n  -k, --installation-key=\u003cvalue\u003e     Installation key for key-protected package. (either --installation-key or\n                                     --installation-key-bypass is required)\n  -n, --version-number=\u003cvalue\u003e       Version number of the package version to be created; overrides the\n                                     sfdx-project.json value.\n  -p, --package=\u003cvalue\u003e              ID (starts with 0Ho) or alias of the package to create a version of.\n  -t, --tag=\u003cvalue\u003e                  Package version’s tag.\n  -v, --target-dev-hub=\u003cvalue\u003e       (required) Username or alias of the Dev Hub org. Not required if the\n                                     `target-dev-hub` configuration variable is already set.\n  -w, --wait=\u003cvalue\u003e                 Number of minutes to wait for the package version to be created.\n  -x, --installation-key-bypass      Bypass the installation key requirement. (either --installation-key or\n                                     --installation-key-bypass is required)\n      --api-version=\u003cvalue\u003e          Override the api version used for api requests made by this command\n      --async-validation             Return a new package version before completing package validations.\n      --generate-pkg-zip             Generate a package ZIP file that you can use for debugging or to examine the\n                                     package contents.\n      --language=\u003cvalue\u003e             Language for the package.\n      --post-install-script=\u003cvalue\u003e  Name of the post-install script; applies to managed packages only.\n      --post-install-url=\u003cvalue\u003e     Post-install instructions URL.\n      --releasenotes-url=\u003cvalue\u003e     Release notes URL.\n      --skip-ancestor-check          Override ancestry requirements, which allows you to specify a package ancestor that\n                                     isn’t the highest released package version.\n      --skip-validation              Skip validation during package version creation; you can’t promote unvalidated\n                                     package versions.\n      --uninstall-script=\u003cvalue\u003e     Uninstall script name; applies to managed packages only.\n      --verbose                      Display verbose command output.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Create a package version in the Dev Hub org.\n\n  The package version is based on the package contents in the specified directory.\n\n  To retrieve details about a package version create request, including status and package version ID (04t), run \"sf\n  package version create report -i 08c...\".\n\n  We recommend that you specify the --installation-key parameter to protect the contents of your package and to prevent\n  unauthorized installation of your package.\n\n  To list package version creation requests in the org, run \"sf package version create list\".\n  To promote a package version to released, you must use the --code-coverage parameter. The package must also meet the\n  code coverage requirements. This requirement applies to both managed and unlocked packages.\n\n  We don’t calculate code coverage for org-dependent unlocked packages, or for package versions that specify\n  --skip-validation.\n\nALIASES\n  $ sf force package version create\n\nEXAMPLES\n  Create a package version from the contents of the \"common\" directory and give it an installation key of\n  \"password123\"; uses your default Dev Hub org:\n\n    $ sf package version create --path common --installation-key password123\n\n  Create a package version from a package with the specified alias; uses the Dev Hub org with username\n  devhub@example.com:\n\n    $ sf package version create --package \"Your Package Alias\" --installation-key password123 --target-dev-hub \\\n      devhub@example.com\n\n  Create a package version from a package with the specified ID:\n\n    $ sf package version create --package 0Ho... --installation-key password123\n\n  Create a package version and skip the validation step:\n\n    $ sf package version create --path common --installation-key password123 --skip-validation\n\n  Create a package version and perform package validations asynchronously:\n\n    $ sf package version create --path common --installation-key password123 --async-validation\n\nFLAG DESCRIPTIONS\n  -c, --code-coverage\n\n    Calculate and store the code coverage percentage by running the packaged Apex tests included in this package\n    version.\n\n    Before you can promote and release a managed or unlocked package version, the Apex code must meet a minimum 75% code\n    coverage requirement. We don’t calculate code coverage for org-dependent unlocked packages or for package versions\n    that specify --skip-validation.\n\n  -f, --definition-file=\u003cvalue\u003e\n\n    Path to a definition file similar to scratch org definition file that contains the list of features and org\n    preferences that the metadata of the package version depends on.\n\n    For a patch version, the features specified in this file are ignored, and instead the features specified for the\n    ancestor version are used.\n\n  -n, --version-number=\u003cvalue\u003e\n\n    Version number of the package version to be created; overrides the sfdx-project.json value.\n\n    For information about the format of the version number, see\n    https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/sfdx_dev2gp_config_file.htm.\n\n  -x, --installation-key-bypass\n\n    Bypass the installation key requirement. (either --installation-key or --installation-key-bypass is required)\n\n    If you bypass this requirement, anyone can install your package.\n\n  --async-validation  Return a new package version before completing package validations.\n\n    Specifying async validation returns the package version earlier in the process, allowing you to install and test the\n    new version right away. If your development team is using continuous integration (CI) scripts, async validation can\n    reduce your overall CI run time.\n\n  --language=\u003cvalue\u003e  Language for the package.\n\n    Specify the language using a language code listed under \"Supported Languages\" in Salesforce Help. If no language is\n    specified, the language defaults to the language of the Dev Hub user who created the package.\n\n  --post-install-script=\u003cvalue\u003e  Name of the post-install script; applies to managed packages only.\n\n    The post-install script is an Apex class within this package that is run in the installing org after installations\n    or upgrades of this package version.\n\n  --post-install-url=\u003cvalue\u003e  Post-install instructions URL.\n\n    The contents of the post-installation instructions URL are displayed in the UI after installation of the package\n    version.\n\n  --releasenotes-url=\u003cvalue\u003e  Release notes URL.\n\n    This link is displayed in the package installation UI to provide release notes for this package version to\n    subscribers.\n\n  --skip-validation  Skip validation during package version creation; you can’t promote unvalidated package versions.\n\n    Skips validation of dependencies, package ancestors, and metadata during package version creation. Skipping\n    validation reduces the time it takes to create a new package version, but you can promote only validated package\n    versions. Skipping validation can suppress important errors that can surface at a later stage. You can specify skip\n    validation or code coverage, but not both. Code coverage is calculated during validation.\n\n  --uninstall-script=\u003cvalue\u003e  Uninstall script name; applies to managed packages only.\n\n    The uninstall script is an Apex class within this package that is run in the installing org after uninstallations of\n    this package.\n\n  --verbose  Display verbose command output.\n\n    Display verbose command output. When polling for the status of the creation, this will output status and timeout\n    data on a separate line for each poll request, which is useful in CI systems where timeouts can occur with long\n    periods of no output from commands.\n```\n\n_See code: [src/commands/package/version/create.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/create.ts)_\n\n## `sf package version create list`\n\nList package version creation requests.\n\n```\nUSAGE\n  $ sf package version create list -v \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-c \u003cvalue\u003e] [-s\n    Queued|InProgress|Success|Error] [--show-conversions-only] [--verbose]\n\nFLAGS\n  -c, --created-last-days=\u003cvalue\u003e  Number of days since the request was created, starting at 00:00:00 of first day to\n                                   now. Use 0 for today.\n  -s, --status=\u003coption\u003e            Status of the version creation request, used to filter the list.\n                                   \u003coptions: Queued|InProgress|Success|Error\u003e\n  -v, --target-dev-hub=\u003cvalue\u003e     (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                   configuration variable is already set.\n      --api-version=\u003cvalue\u003e        Override the api version used for api requests made by this command\n      --show-conversions-only      Filter the list output to display only converted package version.\n      --verbose                    Displays additional information at a slight performance cost, such as the version\n                                   name and number for each package version create request.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  List package version creation requests.\n\n  Shows the details of each request to create a package version in the Dev Hub org.\n\n  All filter parameters are applied using the AND logical operator (not OR).\n\n  To get information about a specific request, run \"sf package version create report\" and supply the request ID.\n\nALIASES\n  $ sf force package version create list\n\nEXAMPLES\n  List all package version creation requests in your default Dev Hub org:\n\n    $ sf package version create list\n\n  List package version creation requests from the last 3 days in the Dev Hub org with username devhub@example.com:\n\n    $ sf package version create list --created-last-days 3 --target-dev-hub\n\n  List package version creation requests with status Error:\n\n    $ sf package version create list --status Error\n\n  List package version creation requests with status InProgress:\n\n    $ sf package version create list --status InProgress\n\n  List package version creation requests with status Success that were created today:\n\n    $ sf package version create list --created-last-days 0 --status Success\n```\n\n_See code: [src/commands/package/version/create/list.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/create/list.ts)_\n\n## `sf package version create report`\n\nRetrieve details about a package version creation request.\n\n```\nUSAGE\n  $ sf package version create report -v \u003cvalue\u003e -i \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -i, --package-create-request-id=\u003cvalue\u003e  (required) ID (starts with 08c) of the package version creation request you\n                                           want to display.\n  -v, --target-dev-hub=\u003cvalue\u003e             (required) Username or alias of the Dev Hub org. Not required if the\n                                           `target-dev-hub` configuration variable is already set.\n      --api-version=\u003cvalue\u003e                Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Retrieve details about a package version creation request.\n\n  Specify the request ID for which you want to view details. If applicable, the command displays errors related to the\n  request.\n\n  To show all requests in the org, run \"sf package version create list\".\n\nALIASES\n  $ sf force package version create report\n\nEXAMPLES\n  Retrieve details about the package version creation request with the specified ID; uses your default Dev Hub org:\n\n    $ sf package version create report --package-create-request-id 08c...\n\n  Retrieve details about the specified package version creation request in the Dev Hub org with username\n  devhub@example.com:\n\n    $ sf package version create report --package-create-request-id 08c... --target-dev-hub devhub@example.com\n```\n\n_See code: [src/commands/package/version/create/report.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/create/report.ts)_\n\n## `sf package version delete`\n\nDelete a package version.\n\n```\nUSAGE\n  $ sf package version delete -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-n]\n\nFLAGS\n  -n, --no-prompt               Don’t prompt before deleting the package version.\n  -p, --package=\u003cvalue\u003e         (required) ID (starts with 04t) or alias of the package version to delete.\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                configuration variable is already set.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Delete a package version.\n\n  Specify the ID or alias of the package version you want to delete. In second-generation managed packaging, only beta\n  package versions can be deleted. Before deleting a package version, review the considerations outlined in\n  https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/sfdx_dev_dev2gp_package_deletion.htm.\n\nALIASES\n  $ sf force package version delete\n\nEXAMPLES\n  Delete a package version with the specified alias using your default Dev Hub org:\n\n    $ sf package version delete --package \"Your Package Alias\"\n\n  Delete a package version with the specified ID using the Dev Hub org with username \"devhub@example.com\":\n\n    $ sf package version delete --package 04t... --target-org devhub@example.com\n```\n\n_See code: [src/commands/package/version/delete.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/delete.ts)_\n\n## `sf package version displayancestry`\n\nDisplay the ancestry tree for a 2GP managed package version.\n\n```\nUSAGE\n  $ sf package version displayancestry -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--dot-code]\n    [--verbose]\n\nFLAGS\n  -p, --package=\u003cvalue\u003e         (required) ID or alias of the package (starts with 0Ho) or package version (starts with\n                                04t) to display ancestry for.\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                configuration variable is already set.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n      --dot-code                Display the ancestry tree in DOT code.\n      --verbose                 Display both the package version ID (starts with 04t) and the version number\n                                (major.minor.patch.build) in the ancestry tree.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nALIASES\n  $ sf force package version displayancestry\n\nEXAMPLES\n  Display the ancestry tree for a package version with the specified alias, using your default Dev Hub org:\n\n    $ sf package version displayancestry --package package_version_alias\n\n  Similar to previous example, but display the output in DOT code:\n\n    $ sf package version displayancestry --package package_version_alias --dot-code\n\n  Display the ancestry tree for a package with the specified ID, using the Dev Hub org with username\n  devhub@example.com:\n\n    $ sf package version displayancestry --package OHo... --target-dev-hub devhub@example.com\n\n  Display the ancestry tree of a package version with the specified ID, using your default Dev Hub org:\n\n    $ sf package version displayancestry --package 04t...\n\nFLAG DESCRIPTIONS\n  -p, --package=\u003cvalue\u003e\n\n    ID or alias of the package (starts with 0Ho) or package version (starts with 04t) to display ancestry for.\n\n    If you specify a package ID (starts with 0Ho) or alias, the ancestor tree for every package version associated with\n    the package ID is displayed. If you specify a package version (starts with 04t) or alias, the ancestry tree of the\n    specified package version is displayed.\n\n  --dot-code  Display the ancestry tree in DOT code.\n\n    You can use the DOT code output in graph visualization software to create tree visualizations.\n```\n\n_See code: [src/commands/package/version/displayancestry.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/displayancestry.ts)_\n\n## `sf package version displaydependencies`\n\nDisplay the dependency graph for an unlocked or 2GP managed package version.\n\n```\nUSAGE\n  $ sf package version displaydependencies -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--edge-direction\n    root-first|root-last] [--verbose]\n\nFLAGS\n  -p, --package=\u003cvalue\u003e          (required) ID or alias of the package version (starts with 04t) or the package version\n                                 create request (starts with 08c) to display the dependency graph for.\n  -v, --target-dev-hub=\u003cvalue\u003e   (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                 configuration variable is already set.\n      --api-version=\u003cvalue\u003e      Override the api version used for api requests made by this command\n      --edge-direction=\u003coption\u003e  [default: root-first] Order (root-first or root-last) in which the dependencies are\n                                 displayed.\n                                 \u003coptions: root-first|root-last\u003e\n      --verbose                  Display both the package version ID (starts with 04t) and the version number\n                                 (major.minor.patch.build) in each node.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nEXAMPLES\n  Display the dependency graph for a package version with the specified alias, using your default Dev Hub org and the\n  default edge-direction:\n\n    $ sf package version displaydependencies --package package_version_alias\n\n  Display the dependency graph for a package version with the specified ID and display the graph using a root-last\n  edge direction. Use the Dev Hub org with username devhub@example.com:\n\n    $ sf package version displaydependencies --package 04t... --edge-direction root-last --target-dev-hub \\\n      devhub@example.com\n\n  Display the dependency graph of a version create request with the specified ID, using your default Dev Hub org and\n  the default edge-direction:\n\n    $ sf package version displaydependencies --package 08c...\n\nFLAG DESCRIPTIONS\n  -p, --package=\u003cvalue\u003e\n\n    ID or alias of the package version (starts with 04t) or the package version create request (starts with 08c) to\n    display the dependency graph for.\n\n    Before running this command, update your sfdx-project.json file to specify the calculateTransitiveDependencies\n    attribute, and set the value to true. This command returns GraphViz code, which can be compiled to a graph using DOT\n    code or another graph visualization software.\n\n  --edge-direction=root-first|root-last  Order (root-first or root-last) in which the dependencies are displayed.\n\n    A root-first graph declares the root as the package that must be installed last. A root-last graph is the reverse\n    order of root-first. If you specify \"--edge-direction root-last\", the graph displays the packages in the order they\n    must be installed. The root starts with the farthest leaf of the package dependencies and ends with the base\n    package, which must be installed last.\n```\n\n_See code: [src/commands/package/version/displaydependencies.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/displaydependencies.ts)_\n\n## `sf package version list`\n\nList all package versions in the Dev Hub org.\n\n```\nUSAGE\n  $ sf package version list -v \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-c \u003cvalue\u003e] [--concise]\n    [--show-conversions-only] [-m \u003cvalue\u003e] [-p \u003cvalue\u003e] [-r] [-b \u003cvalue\u003e] [-o \u003cvalue\u003e] [--verbose]\n\nFLAGS\n  -b, --branch=\u003cvalue\u003e              Branch in your source control system used to filter the results; only package\n                                    versions based on the specified branch are listed.\n  -c, --created-last-days=\u003cvalue\u003e   Number of days since the request was created, starting at 00:00:00 of first day to\n                                    now. Use 0 for today.\n  -m, --modified-last-days=\u003cvalue\u003e  Number of days since the items were modified, starting at 00:00:00 of first day to\n                                    now. Use 0 for today.\n  -o, --order-by=\u003cvalue\u003e            Package version fields used to order the list.\n  -p, --packages=\u003cvalue\u003e            Comma-delimited list of packages (aliases or 0Ho IDs) to list.\n  -r, --released                    Display released versions only (IsReleased=true).\n  -v, --target-dev-hub=\u003cvalue\u003e      (required) Username or alias of the Dev Hub org. Not required if the\n                                    `target-dev-hub` configuration variable is already set.\n      --api-version=\u003cvalue\u003e         Override the api version used for api requests made by this command\n      --concise                     Display limited package version details.\n      --show-conversions-only       Filter the list output to display only converted package version.\n      --verbose                     Display extended package version details.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  List all package versions in the Dev Hub org.\n\n  Description\n\nALIASES\n  $ sf force package version list\n\nEXAMPLES\n  List package versions in your default Dev Hub org that were created in the last 3 days; show only the released\n  versions and order the list using the PatchVersion field. Display extended details about each package version:\n\n    $ sf package version list --verbose --created-last-days 3 --released --order-by PatchVersion\n\n  List the released package versions for the two specified packages that were modified today; use the Dev Hub org with\n  username devhub@example.com:\n\n    $ sf package version list --packages 0Ho000000000000,0Ho000000000001 --released --modified-last-days 0 \\\n      --target-dev-hub devhub@example.com\n\n  List all released package versions in your default Dev Hub org:\n\n    $ sf package version list --released\n\n  List package versions that were modified today in your default Dev Hub org; show limited details about each one:\n\n    $ sf package version list --concise --modified-last-days 0\n\n  List package versions that are based on the \"featureA\" branch in your source control system that were modified today\n  in your default Dev Hub org; show limited details about each one:\n\n    $ sf package version list --concise --modified-last-days 0 --branch featureA\n\n  List released package versions that were created in the last 3 days in your default Dev Hub org; show limited\n  details:\n\n    $ sf package version list --concise --created-last-days 3 --released\n\n  List released package versions that were modified today for the two packages with specified aliases in your default\n  Dev Hub org:\n\n    $ sf package version list --packages exp-mgr,exp-mgr-util --released --modified-last-days 0\n```\n\n_See code: [src/commands/package/version/list.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/list.ts)_\n\n## `sf package version promote`\n\nPromote a package version to released.\n\n```\nUSAGE\n  $ sf package version promote -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-n]\n\nFLAGS\n  -n, --no-prompt               Don't prompt to confirm setting the package version as released.\n  -p, --package=\u003cvalue\u003e         (required) ID (starts with 04t) or alias of the package version to promote.\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                configuration variable is already set.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Promote a package version to released.\n\n  Supply the ID or alias of the package version you want to promote. Promotes the package version to released status.\n\nALIASES\n  $ sf force package version promote\n\nEXAMPLES\n  Promote the package version with the specified ID to released; uses your default Dev Hub org:\n\n    $ sf package version promote --package 04t...\n\n  Promote the package version with the specified alias to released; uses the Dev Hub org with username\n  devhub@example.com:\n\n    $ sf package version promote --package awesome_package_alias --target-dev-hub devhub@example.com\n\n  Promote the package version with an alias that has spaces to released:\n\n    $ sf package version promote --package \"Awesome Package Alias\"\n```\n\n_See code: [src/commands/package/version/promote.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/promote.ts)_\n\n## `sf package version report`\n\nRetrieve details about a package version in the Dev Hub org.\n\n```\nUSAGE\n  $ sf package version report -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--verbose]\n\nFLAGS\n  -p, --package=\u003cvalue\u003e         (required) ID (starts with 04t) or alias of the package to retrieve details for.\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                configuration variable is already set.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n      --verbose                 Display extended package version details.\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Retrieve details about a package version in the Dev Hub org.\n\n  To update package version values, run \"sf package version update\".\n\nALIASES\n  $ sf force package version report\n\nEXAMPLES\n  Retrieve details about the package version with the specified ID from your default Dev Hub org:\n\n    $ sf package version report --package 04t...\n\n  Retrieve details about the package version with the specified alias (that contains spaces) from the Dev Hub org with\n  username devhub@example.com:\n\n    $ sf package version report --package \"Your Package Alias\" --target-dev-hub devhub@example.com\n```\n\n_See code: [src/commands/package/version/report.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/report.ts)_\n\n## `sf package version retrieve`\n\nRetrieve package metadata for a specified package version. Package metadata can be retrieved for only second-generation managed package versions or unlocked packages.\n\n```\nUSAGE\n  $ sf package version retrieve -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-d\n  \u003cvalue\u003e]\n\nFLAGS\n  -d, --output-dir=\u003cvalue\u003e      [default: force-app] Path within your Salesforce DX project directory in which to\n                                download the metadata. This directory must be empty.\n  -p, --package=\u003cvalue\u003e         (required) Subscriber package version ID (starts with 04t).\n  -v, --target-dev-hub=\u003cvalue\u003e  (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`\n                                configuration variable is already set.\n      --api-version=\u003cvalue\u003e     Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Retrieve package metadata for a specified package version. Package metadata can be retrieved for only\n  second-generation managed package versions or unlocked packages.\n\n  Retrieving a package version downloads the metadata into the directory you specify.\n\n  When you run this command, specify the subscriber package version ID (starts with 04t) and the path to an empty\n  directory.\n\n  By default, the package version retrieve command is available to 2GP managed packages that were converted from 1GP. To\n  use this command with a managed package created using 2GP (not converted from 1GP) or with an unlocked package,\n  specify IsDevUsePkgZipRequested = true in the Package2VersionCreateRequest Tooling API object. If you run this command\n  and the zip folder with the package version’s source files is missing, confirm that IsDevUsePkgZipRequested is set to\n  true.\n\nEXAMPLES\n  Retrieve package metadata for a converted subscriber package version ID (starts with 04t) into my-directory/ within\n  your Salesforce DX project directory:\n\n    $ sf package version retrieve --package 04tXXX --output-dir my-directory/ --target-dev-hub devhub@example.com\n```\n\n_See code: [src/commands/package/version/retrieve.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/retrieve.ts)_\n\n## `sf package version update`\n\nUpdate a package version.\n\n```\nUSAGE\n  $ sf package version update -v \u003cvalue\u003e -p \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-a \u003cvalue\u003e] [-e\n    \u003cvalue\u003e] [-b \u003cvalue\u003e] [-t \u003cvalue\u003e] [-k \u003cvalue\u003e]\n\nFLAGS\n  -a, --version-name=\u003cvalue\u003e         New package version name.\n  -b, --branch=\u003cvalue\u003e               New package version branch.\n  -e, --version-description=\u003cvalue\u003e  New package version description.\n  -k, --installation-key=\u003cvalue\u003e     New installation key for key-protected package (default: null)\n  -p, --package=\u003cvalue\u003e              (required) ID (starts with 04t) or alias of the package to update a version of.\n  -t, --tag=\u003cvalue\u003e                  New package version tag.\n  -v, --target-dev-hub=\u003cvalue\u003e       (required) Username or alias of the Dev Hub org. Not required if the\n                                     `target-dev-hub` configuration variable is already set.\n      --api-version=\u003cvalue\u003e          Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Update a package version.\n\n  Specify a new value for each option you want to update.\n\n  To display details about a package version, run \"sf package version display\".\n\nALIASES\n  $ sf force package version update\n\nEXAMPLES\n  Update the package version that has the specified alias (that contains spaces) with a new installation key\n  \"password123\"; uses your default Dev Hub org:\n\n    $ sf package version update --package \"Your Package Alias\" --installation-key password123\n\n  Update the package version that has the specified ID with a new branch and tag; use the Dev Hub org with username\n  devhub@example.com:\n\n    $ sf package version update --package 04t... --branch main --tag 'Release 1.0.7' --target-dev-hub \\\n      devhub@example.com\n\n  Update the package version that has the specified ID with a new description:\n\n    $ sf package version update --package 04t... --version-description \"New Package Version Description\"\n```\n\n_See code: [src/commands/package/version/update.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package/version/update.ts)_\n\n## `sf package1 version create`\n\nCreate a first-generation package version in the release org.\n\n```\nUSAGE\n  $ sf package1 version create -o \u003cvalue\u003e -i \u003cvalue\u003e -n \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-d\n    \u003cvalue\u003e] [-v \u003cvalue\u003e] [-m] [-r \u003cvalue\u003e] [-p \u003cvalue\u003e] [-k \u003cvalue\u003e] [-w \u003cvalue\u003e]\n\nFLAGS\n  -d, --description=\u003cvalue\u003e        Package version description.\n  -i, --package-id=\u003cvalue\u003e         (required) ID of the metadata package (starts with 033) of which you’re creating a\n                                   new version.\n  -k, --installation-key=\u003cvalue\u003e   Installation key for key-protected package (default: null).\n  -m, --managed-released           Create a managed package version.\n  -n, --name=\u003cvalue\u003e               (required) Package version name.\n  -o, --target-org=\u003cvalue\u003e         (required) Username or alias of the target org. Not required if the `target-org`\n                                   configuration variable is already set.\n  -p, --post-install-url=\u003cvalue\u003e   Post install URL.\n  -r, --release-notes-url=\u003cvalue\u003e  Release notes URL.\n  -v, --version=\u003cvalue\u003e            Package version in major.minor format, for example, 3.2.\n  -w, --wait=\u003cvalue\u003e               Minutes to wait for the package version to be created (default: 2 minutes).\n      --api-version=\u003cvalue\u003e        Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Create a first-generation package version in the release org.\n\n  The package version is based on the contents of the specified metadata package. Omit --managed-released if you want to\n  create an unmanaged package version.\n\nALIASES\n  $ sf force package1 version create\n\nEXAMPLES\n  Create a first-generation package version from the package with the specified ID and name the package version\n  \"example\"; use your default org:\n\n    $ sf package1 version create --package-id 033... --name example\n\n  Same as previous example, but provide a description and wait for 30 minutes for the package version to be created;\n  use the specified org:\n\n    $ sf package1 version create --package-id 033... --name example --description \"example description\" --wait 30 \\\n      --target-org myorg@example.com\n\nFLAG DESCRIPTIONS\n  -m, --managed-released  Create a managed package version.\n\n    To create a beta version, don’t include this parameter.\n\n  -p, --post-install-url=\u003cvalue\u003e  Post install URL.\n\n    The contents of the post-installation instructions URL are displayed in the UI after installation of the package\n    version.\n\n  -r, --release-notes-url=\u003cvalue\u003e  Release notes URL.\n\n    This link is displayed in the package installation UI to provide release notes for this package version to\n    subscribers.\n```\n\n_See code: [src/commands/package1/version/create.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package1/version/create.ts)_\n\n## `sf package1 version create get`\n\nRetrieve the status of a package version creation request.\n\n```\nUSAGE\n  $ sf package1 version create get -o \u003cvalue\u003e -i \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -i, --request-id=\u003cvalue\u003e   (required) ID of the PackageUploadRequest (starts with 0HD).\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nALIASES\n  $ sf force package1 version create get\n\nEXAMPLES\n  Get the status of the creation request for the package version with the specified ID in your default org:\n\n    $ sf package1 version create get --request-id 0HD...\n\n  Same as previous example, but use the specified org:\n\n    $ sf package1 version create get --request-id 0HD... --target-org myorg@example.com\n```\n\n_See code: [src/commands/package1/version/create/get.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package1/version/create/get.ts)_\n\n## `sf package1 version display`\n\nDisplay details about a first-generation package version.\n\n```\nUSAGE\n  $ sf package1 version display -o \u003cvalue\u003e -i \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -i, --package-version-id=\u003cvalue\u003e  (required) ID (starts with 04t) of the metadata package version whose details you\n                                    want to display.\n  -o, --target-org=\u003cvalue\u003e          (required) Username or alias of the target org. Not required if the `target-org`\n                                    configuration variable is already set.\n      --api-version=\u003cvalue\u003e         Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nALIASES\n  $ sf force package1 version display\n\nEXAMPLES\n  Display details about the first-generation package version with the specified ID in your default org:\n\n    $ sf package1 version display --package-version-id 04t...\n\n  Same as previous example, but use the specified org:\n\n    $ sf package1 version display --package-version-id 04t... --target-org myorg@example.com\n```\n\n_See code: [src/commands/package1/version/display.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package1/version/display.ts)_\n\n## `sf package1 version list`\n\nList package versions for the specified first-generation package or for the org.\n\n```\nUSAGE\n  $ sf package1 version list -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-i \u003cvalue\u003e]\n\nFLAGS\n  -i, --package-id=\u003cvalue\u003e   Metadata package ID (starts with 033) whose package versions you want to list.\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nALIASES\n  $ sf force package1 version list\n\nEXAMPLES\n  List all first-generation package versions in your default org:\n\n    $ sf package1 version list\n\n  List package versions for the specified first-generation package in the specifief org:\n\n    $ sf package1 version list --package-id 033... --target-org myorg@example.com\n\nFLAG DESCRIPTIONS\n  -i, --package-id=\u003cvalue\u003e  Metadata package ID (starts with 033) whose package versions you want to list.\n\n    If not specified, shows all versions for all packages (managed and unmanaged) in the org.\n```\n\n_See code: [src/commands/package1/version/list.ts](https://github.com/salesforcecli/plugin-packaging/blob/2.28.6/src/commands/package1/version/list.ts)_\n\n\u003c!-- commandsstop --\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsalesforcecli%2Fplugin-packaging","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsalesforcecli%2Fplugin-packaging","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsalesforcecli%2Fplugin-packaging/lists"}