# Recommend a Specific Package Version to Your Subscribers

You can choose to recommend that your subscribers upgrade to a specific, released version of your package.

When you set a package version as the recommended version, your subscribers see an **Upgrade to Recommended Version** option on the Installed Packages page in their org.

![The Upgrade to Recommended Version link on a subscriber's Installed Package page](https://a.sfdcstatic.com/developer-website/sfdocs/platform-pkg-exchange/media/pkg2\_dev/pkg2\_recommended_version.png)

To set a package’s recommended version, run the `sf package update` CLI command and specify the package version in the `--recommended-version-id` flag. This example sets `PackageA@1.0` as the recommended version.

```nolang
sf package update --package 0Ho.. --target-dev-hub devhub@example.com --recommended-version-id PackageA@1.0
```

Keep in mind these requirements and considerations for setting a recommended version:

- You can set one recommended version per package.
- Only released package versions can be set as the recommended version.
- The recommended version is not required to be the latest, released version of a package.
- When you update the recommended version, the new version that you set must be a descendant of the previous version in the [package ancestry](https://developer.salesforce.com/docs/atlas.en-us.pkg2\_dev.meta/pkg2\_dev/sfdx_dev_dev2gp_package_ancestor_intro.htm). If the package versions don’t share an ancestry tree, you’ll get an error when you try to update the package’s recommended version. To bypass this error, you can use the `sf package update` CLI command’s `--skip-ancestor-check` flag.

**See Also**

- [Release a Second-Generation Managed Package](/docs/platform/pkg2-dev/guide/sfdx-dev-dev2gp-create-pkg-ver-promote.md)
- [*Salesforce CLI Command Reference*: package update](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_package_commands_unified.htm#cli_reference_package_update_unified)