---
schema_version: "1"
id: a5fb0ff3c43157202a6f3b6223ea4a966aa505b679413f3f4f7599d68d52e027
title: CLI Deprecation Policy
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/sfdx-setup/guides/sfdx-dev/workspace-setup/sfdx-dev-cli-deprecation.md
canonical_url: https://developer.salesforce.com/docs/platform/sfdx-setup/guide/sfdx-dev-cli-deprecation.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: f2cfd30d510f54234bd28c5a2ad7d732703b5ee57835c616cef5c42229a12f76
products:
  - Salesforce CLI Setup Guide
  - salesforcedx
---

# CLI Deprecation Policy

Salesforce deprecates CLI commands and flags when, for example, the underlying API changes.

The Salesforce CLI deprecation policy is:

- Salesforce announces new and upcoming deprecations of commands and flags in the weekly Salesforce CLI release notes.
- Salesforce can deprecate a command or flag at any time.
- When you run the deprecated command, Salesforce provides a deprecation warning for a minimum of 4 months.
- Salesforce removes the deprecated command or flag 4 months, or more, after the deprecation warning first appears.
- If you use a command or flag that’s been deprecated but not yet removed, you get a warning message in `stderr` in the human-readable output. If you specify JSON output, the warning is presented as a property. The message includes the plugin version in which we plan to remove the command or flag. The command help also includes deprecation information when appropriate.
- When possible, Salesforce provides a functional alternative to the deprecated command or flag.
- For our policy on changes to a Salesforce CLI command’s JSON response, see [Support for JSON Responses](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_json_support.htm).

**See Also**

- [Salesforce CLI Weekly Release Notes](https://github.com/forcedotcom/cli/blob/main/releasenotes/README.md)