@salesforce/cli 2.73.5 → 2.73.6

package/README.md

@@ -24,7 +24,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.73.5 linux-x64 node-v22.12.0
+@salesforce/cli/2.73.6 linux-x64 node-v22.12.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -3200,7 +3200,7 @@ FLAG DESCRIPTIONS
     You can specify either --source-sandbox-name or --source-id when cloning an existing sandbox, but not both.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/create/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/create/sandbox.ts)_
 
 ## `sf org create scratch`
 
@@ -3354,7 +3354,7 @@ FLAG DESCRIPTIONS
     Omit this flag to have Salesforce generate a unique username for your org.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/create/scratch.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/create/scratch.ts)_
 
 ## `sf org create user`
 
@@ -3508,7 +3508,7 @@ EXAMPLES
     $ sf org delete sandbox --target-org my-sandbox --no-prompt
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/delete/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/delete/sandbox.ts)_
 
 ## `sf org delete scratch`
 
@@ -3552,7 +3552,7 @@ EXAMPLES
     $ sf org delete scratch --target-org my-scratch-org --no-prompt
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/delete/scratch.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/delete/scratch.ts)_
 
 ## `sf org disable tracking`
 
@@ -3591,7 +3591,7 @@ EXAMPLES
     $ sf org disable tracking
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/disable/tracking.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/disable/tracking.ts)_
 
 ## `sf org display`
 
@@ -3636,7 +3636,7 @@ EXAMPLES
     $ sf org display --target-org TestOrg1 --verbose
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/display.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/display.ts)_
 
 ## `sf org display user`
 
@@ -3717,7 +3717,7 @@ EXAMPLES
     $ sf org enable tracking
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/enable/tracking.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/enable/tracking.ts)_
 
 ## `sf org generate password`
 
@@ -3823,7 +3823,7 @@ EXAMPLES
     $ sf org list --clean
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/list.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/list.ts)_
 
 ## `sf org list auth`
 
@@ -3962,7 +3962,7 @@ FLAG DESCRIPTIONS
     Examples of metadata types that use folders are Dashboard, Document, EmailTemplate, and Report.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/list/metadata.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/list/metadata.ts)_
 
 ## `sf org list metadata-types`
 
@@ -4017,7 +4017,7 @@ FLAG DESCRIPTIONS
     Override the api version used for api requests made by this command
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/list/metadata-types.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/list/metadata-types.ts)_
 
 ## `sf org list sobject record-counts`
 
@@ -4600,7 +4600,7 @@ EXAMPLES
     $ sf org open --source-file force-app/main/default/bots/Coral_Cloud_Agent/Coral_Cloud_Agent.bot-meta.xml
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/open.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/open.ts)_
 
 ## `sf org open agent`
 
@@ -4651,7 +4651,7 @@ EXAMPLES
     $ sf org open agent --target-org MyTestOrg1 --browser firefox --name Coral_Cloud_Agent
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/open/agent.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/open/agent.ts)_
 
 ## `sf org refresh sandbox`
 
@@ -4728,7 +4728,7 @@ FLAG DESCRIPTIONS
     By default, a sandbox auto-activates after a refresh. Use this flag to control sandbox activation manually.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/refresh/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/refresh/sandbox.ts)_
 
 ## `sf org resume sandbox`
 
@@ -4791,7 +4791,7 @@ FLAG DESCRIPTIONS
     returns the job ID. To resume checking the sandbox creation, rerun this command.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/resume/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/resume/sandbox.ts)_
 
 ## `sf org resume scratch`
 
@@ -4838,7 +4838,7 @@ FLAG DESCRIPTIONS
     The job ID is valid for 24 hours after you start the scratch org creation.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.17/src/commands/org/resume/scratch.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.2.18/src/commands/org/resume/scratch.ts)_
 
 ## `sf package create`
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/cli",
-  "version": "2.73.5",
+  "version": "2.73.6",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/cli",
-      "version": "2.73.5",
+      "version": "2.73.6",
       "hasInstallScript": true,
       "license": "BSD-3-Clause",
       "dependencies": {
@@ -32,7 +32,7 @@
         "@salesforce/plugin-info": "3.4.32",
         "@salesforce/plugin-limits": "3.3.44",
         "@salesforce/plugin-marketplace": "1.3.7",
-        "@salesforce/plugin-org": "5.2.17",
+        "@salesforce/plugin-org": "5.2.18",
         "@salesforce/plugin-packaging": "2.9.12",
         "@salesforce/plugin-schema": "3.3.46",
         "@salesforce/plugin-settings": "2.4.10",
@@ -9345,9 +9345,9 @@
       }
     },
     "node_modules/@salesforce/plugin-org": {
-      "version": "5.2.17",
-      "resolved": "https://registry.npmjs.org/@salesforce/plugin-org/-/plugin-org-5.2.17.tgz",
-      "integrity": "sha512-u+Zd2aF0bdNnD+T8+cRai2B9y2AQdAGj8qtEg2kXsELVy/1rkPxwsQxflyzHdfATM6I1L9w65XDIX55fII76gQ==",
+      "version": "5.2.18",
+      "resolved": "https://registry.npmjs.org/@salesforce/plugin-org/-/plugin-org-5.2.18.tgz",
+      "integrity": "sha512-9GH+tA3yTj5K1z3B5YQkDWPqMzizfL/mpfWsfeI/KHBby546WDdtqkwaP1xATPIo9wwSfe27tuOCCwjKzYIMJw==",
       "license": "BSD-3-Clause",
       "dependencies": {
         "@oclif/core": "^4.2.2",

package/oclif.lock

@@ -2648,10 +2648,10 @@
     got "^13.0.0"
     proxy-agent "^6.4.0"
 
-"@salesforce/plugin-org@5.2.17":
-  version "5.2.17"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-org/-/plugin-org-5.2.17.tgz"
-  integrity sha512-u+Zd2aF0bdNnD+T8+cRai2B9y2AQdAGj8qtEg2kXsELVy/1rkPxwsQxflyzHdfATM6I1L9w65XDIX55fII76gQ==
+"@salesforce/plugin-org@5.2.18":
+  version "5.2.18"
+  resolved "https://registry.npmjs.org/@salesforce/plugin-org/-/plugin-org-5.2.18.tgz"
+  integrity sha512-9GH+tA3yTj5K1z3B5YQkDWPqMzizfL/mpfWsfeI/KHBby546WDdtqkwaP1xATPIo9wwSfe27tuOCCwjKzYIMJw==
   dependencies:
     "@oclif/core" "^4.2.2"
     "@oclif/multi-stage-output" "^0.8.1"

package/oclif.manifest.json

@@ -1,5 +1,295 @@
 {
   "commands": {
+    "code-analyzer:config": {
+      "aliases": [],
+      "args": {},
+      "description": "Code Analyzer gives you the ability to configure settings that modify Code Analyzer's behavior, to override the tags and severity levels of rules, and to configure the engine specific settings.  Use this command to see the current state of this configuration. You can also save this state to a YAML-formatted file that you can modify for your needs.\n\nTo apply a custom configuration with Code Analyzer, either keep your custom configuration settings in a `code-analyzer.yml` file located in the current folder from which you are executing commands, or specify the location of your custom configuration file to the Code Analyzer commands with the --config-file flag.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.",
+      "examples": [
+        "Display the current state of the Code Analyzer configuration using the default behavior: display top level configuration, display the engine and rule override settings associated with all the rules that have a \"Recommended\" tag; and automatically apply any existing custom configuration settings found in a `code-analyzer.yml` or `code-analyzer.yaml` file in the current folder:\n<%= config.bin %> <%= command.id %>",
+        "This example is identical to the previous one, assuming that `./code-analyzer.yml` exists in your current folder.\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer.yml --rule-selector Recommended",
+        "Write the current state of configuration to the file `code-analyzer.yml`, including any configuration from an existing `code-analyzer.yml` file. The command preserves all values from the original config, but overwrites any comments:\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer.yml --output-file code-analyzer.yml",
+        "Display the configuration state for all rules, instead of just the recommended ones:\n<%= config.bin %> <%= command.id %> --rule-selector all",
+        "Display the configuration state associated with recommended rules that are applicable to your workspace folder, `./src`:\n<%= config.bin %> <%= command.id %> --workspace ./src",
+        "Display any relevant configuration settings associated with the rule name 'no-undef' from the 'eslint' engine:\n<%= config.bin %> <%= command.id %> --rule-selection eslint:no-undef",
+        "Load an existing configuration file called `existing-config.yml`, and then write the configuration to a new file called `new-config.yml`, the configuration state that is applicable to all rules that are relevant to the workspace located in the current folder:\n<%= config.bin %> <%= command.id %> --config-file ./existing-config.yml --rule-selection all --workspace . --output-file ./subfolder-config.yml"
+      ],
+      "flags": {
+        "workspace": {
+          "char": "w",
+          "description": "Use the --workspace flag to display only the configuration associated with the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.\n\nThis command uses the type of file in the workspace, such as JavaScript or Typescript, to determine the rules to include in the configuration state. For example, if your workspace contains only JavaScript files, the command doesn't include TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines may be configured to add additional rules based on what it finds in your workspace.  For example, if you set the \"engines.eslint.auto_discover_eslint_config\" value of your `code-analyzer.yml` file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.",
+          "name": "workspace",
+          "summary": "Set of files you want to include in the code analysis.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "rule-selector": {
+          "char": "r",
+          "description": "Use the --rule-selector flag to display only the configuration associated with the rules based on specific criteria. You can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names.\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection.  For example, \"--rule-selector eslint:Security\" reduces the output to only contain the configuration state associated with the rules from the \"eslint\" engine that have the \"Security\" tag. To add multiple rule selectors together (a union), specify the --rule-selector flag multiple times, such as \"--rule-selector eslint:Recommended --rule-selector retire-js:3\".\n\nIf you don't specify this flag, then the command uses the \"Recommended\" tag rule selector.\n\nRun `<%= config.bin %> <%= command.id %>  --rule-selector all` to display the configuration state associated with all possible rules available, and not just the recommended ones.",
+          "name": "rule-selector",
+          "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
+          "default": [
+            "Recommended"
+          ],
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "config-file": {
+          "char": "c",
+          "description": "Use this flag to apply the customizations from a custom Code Analyzer configuration file to be displayed alongside the current Code Analyzer configuration state.\n\nIf you don't specify this flag, then the command looks for and applies a file named `code-analyzer.yml` or `code-analyzer.yaml` in your current folder.",
+          "name": "config-file",
+          "summary": "Path to the existing configuration file used to customize the engines and rules.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "output-file": {
+          "char": "f",
+          "description": "Use this flag to write the final config to a file, in addition to the terminal.",
+          "name": "output-file",
+          "summary": "Output file to write the configuration state to. The file is written in YAML format.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "code-analyzer:config",
+      "pluginAlias": "@salesforce/plugin-code-analyzer",
+      "pluginName": "@salesforce/plugin-code-analyzer",
+      "pluginType": "jit",
+      "state": "Beta",
+      "strict": true,
+      "summary": "Display the current state of configuration for Code Analyzer.",
+      "enableJsonFlag": false,
+      "SF_ENV": "SF_ENV",
+      "isESM": false,
+      "relativePath": [
+        "lib",
+        "commands",
+        "code-analyzer",
+        "config.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "code-analyzer:config",
+        "config:code-analyzer"
+      ]
+    },
+    "code-analyzer:rules": {
+      "aliases": [],
+      "args": {},
+      "description": "You can also view details about the rules, such as the engine it's associated with, tags, and description.\n\nUse this command to determine the exact set of rules to analyze your code. The `code-analyzer run` command has similar flags as this command, so once you've determined the flag values for this command that list the rules you want to run, you specify the same values to the `code-analyzer run` command.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.",
+      "examples": [
+        "List rules using the default behavior: include rules from all engines that have a \"Recommended\" tag; display the rules using concise table format; and automatically apply rule or engine overrides if a \"code-analyzer.yml\" or \"code-analyzer.yaml\" file exists in the current folder:\n<%= config.bin %> <%= command.id %>",
+        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --view table --config-file ./code-analyzer.yml",
+        "List the recommended rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:Recommended",
+        "List all the rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint",
+        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:all",
+        "List all rules for all engines:\n<%= config.bin %> <%= command.id %>  --rule-selector all",
+        "Get a more accurate list of the rules that apply specifically to your workspace (all the files in the current folder):\n<%= config.bin %> <%= command.id %>  --rule-selector all --workspace .",
+        "List the recommended rules associated with a workspace that includes all the files in the folder \"./other-source\" and only the Apex class files (extension .cls) under the folder \"./force-app\":\n<%= config.bin %> <%= command.id %>  --rule-selector Recommended --workspace ./other-source --workspace ./force-app/**/*.cls",
+        "List all the \"eslint\" engine rules that have a moderate severity (3) and the recommended \"retire-js\" engine rules with any severity:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended",
+        "Similar to the previous example, but apply the rule overrides and engine settings from the configuration file called \"code-analyzer2.yml\" in the current folder. If, for example, you changed the severity of an \"eslint\" rule from moderate (3) to high (2) in the configuration file, then that rule won't be listed:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended --config-file ./code-analyzer2.yml",
+        "List the details of the \"getter-return\" rule of the \"eslint\" engine and the rules named \"no-inner-declarations\" in any engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:getter-return --rule-selector no-inner-declarations --view detail",
+        "List the details of the recommended \"eslint\" engine rules that have the tag \"problem\" and high severity level (2) that apply to your workspace folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector eslint:Recommended:problem:2 --view detail --workspace ./force-app"
+      ],
+      "flags": {
+        "workspace": {
+          "char": "w",
+          "description": "If you specify this flag, the command returns a more accurate list of the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders. \n\nThis command uses the type of file in the workspace, such as JavaScript or Typescript, to determine the rules to list. For example, if your workspace contains only JavaScript files, the command doesn't list TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines may be configured to add additional rules based on what it finds in your workspace.  For example, if you set the engines.eslint.auto_discover_eslint_config value of your code-analyzer.yml file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.",
+          "name": "workspace",
+          "summary": "Set of files you want to include in the code analysis.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "rule-selector": {
+          "char": "r",
+          "description": "Use the --rule-selector flag to select the list of rules based on specific criteria.  For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\". \n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection.  For example, \"--rule-selector eslint:Security\" lists rules associated only with the \"eslint\" engine that have the Security tag.  The flag \"--rule-selector eslint:Security:3\" flag lists the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the --rule-selector flag multiple times, such as \"--rule-selector eslint:Recommended --rule-selector retire-js:3\".\n\nRun `<%= config.bin %> <%= command.id %>  --rule-selector all` to list see the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
+          "name": "rule-selector",
+          "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
+          "default": [
+            "Recommended"
+          ],
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "config-file": {
+          "char": "c",
+          "description": "Code Analyzer has an internal default configuration for its rule and engine properties. If you want to override these defaults, you can create a Code Analyzer configuration file.\n\nWe recommend that you name your Code Analyzer configuration file \"code-analyzer.yml\" or \"code-analyzer.yaml\" and put it at the root of your workspace. You then don't need to use this flag when you run the `<%= command.id %>` command from the root of your workspace, because it automatically looks for either file in the current folder, and if found, applies its rule overrides and engine settings. If you want to name the file something else, or put it in an alternative folder, then you must specify this flag.\n\nTo help you get started, use the `code-analyzer config` command to create your first Code Analyzer configuration file. With it, you can change the severity of an existing rule, change a rule's tags, and so on. Then use this flag to specify the file so that the command takes your customizations into account.",
+          "name": "config-file",
+          "summary": "Path to the configuration file used to customize the engines and rules.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "view": {
+          "char": "v",
+          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information.",
+          "name": "view",
+          "summary": "Format to display the rules in the terminal.",
+          "default": "table",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "detail",
+            "table"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "code-analyzer:rules",
+      "pluginAlias": "@salesforce/plugin-code-analyzer",
+      "pluginName": "@salesforce/plugin-code-analyzer",
+      "pluginType": "jit",
+      "state": "Beta",
+      "strict": true,
+      "summary": "List the rules that are available to analyze your code.",
+      "enableJsonFlag": false,
+      "SF_ENV": "SF_ENV",
+      "isESM": false,
+      "relativePath": [
+        "lib",
+        "commands",
+        "code-analyzer",
+        "rules.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "code-analyzer:rules",
+        "rules:code-analyzer"
+      ]
+    },
+    "code-analyzer:run": {
+      "aliases": [],
+      "args": {},
+      "description": "You can scan your codebase with the recommended rules. Or use flags to filter the rules based on engines (such as \"retire-js\" or \"eslint\"), rule names, tags, and more. \n\nIf you want to preview the list of rules before you actually run them, use the `code-analyzer rules` command, which also has the \"--rules-selector\", \"--workspace\", and \"--config-file\" flags that together define the list of rules to be run.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.",
+      "examples": [
+        "Analyze code using the default behavior: analyze the files in the current folder (default workspace) using the Recommended rules; display the output in the terminal with the concise table view; and automatically apply rule or engine overrides if a \"code-analyzer.yml\" or \"code-analyzer.yaml\" file exists in the current folder:\n<%= config.bin %> <%= command.id %>",
+        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --workspace . --view table --config-file ./code-analyzer.yml",
+        "Analyze the files using the recommended \"eslint\" rules and show details of the violations:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:Recommended --view detail",
+        "Analyze the files using all the \"eslint\" rules:\n<%= config.bin %> <%= command.id %> --rule-selector eslint",
+        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:all",
+        "Analyze the files using all rules for all engines:\n<%= config.bin %> <%= command.id %> --rule-selector all",
+        "Analyze files using the recommended \"retire-js\" rules analyze in a workspace that consists of all files in the folder \"./other-source\" and only the Apex class files (extension .cls) in the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector retire-js:Recommended --workspace ./other-source --workspace ./force-app/**/*.cls",
+        "Specify a custom configuration file and output the results to the \"results.csv\" file in CSV format; the commands fails if it finds a violation that exceeds the moderate severity level (3):\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer2.yml --output-file results.csv --severity-threshold 3",
+        "Analyze the files using all the \"eslint\" engine rules that have a moderate severity (3) and the recommended \"retire-js\" engine rules with any severity:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended",
+        "Analyze the files using only the \"getter-return\" rule of the \"eslint\" engine and any rule named \"no-inner-declarations\" from any engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:getter-return --rule-selector no-inner-declarations"
+      ],
+      "flags": {
+        "workspace": {
+          "char": "w",
+          "description": "Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.",
+          "name": "workspace",
+          "summary": "Set of files you want to include in the code analysis.",
+          "default": [
+            "."
+          ],
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "path-start": {
+          "char": "s",
+          "description": "If you don't specify this flag, then any path-based analysis rules automatically discover and use all starting points found in your workspace. Use this flag to restrict the starting points to only those you want in your code analysis. \n\nThis flag only applies to path-based analysis rules, which are of type DataFlow and Flow. These types of rules are only available from some engines, like the Salesforce Graph Engine, \"sfge\" for example.\n\nIf you specify a file or a folder as your starting point, then the analysis uses only the methods that have public or global accessibility. \n\nTo specify individual methods as a starting point, use the syntax \"<file>#methodName\" to select a single method or \"<file>#methodName1;methodName2\" to select multiple methods. For example, \"SomeClass.cls#method1\" (single method) or \"SomeClass.cls#method1;method2\" (multiple methods).\n\nYou can use glob patterns (wildcards) only when specifying files and folders; you can't use glob patterns when specifying individual methods.",
+          "hidden": true,
+          "name": "path-start",
+          "summary": "Starting points within your workspace to restrict any path-based analysis rules to.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "rule-selector": {
+          "char": "r",
+          "description": "Use the --rule-selector flag to select the list of rules to run based on specific criteria.  For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\".\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection.  For example, \"--rule-selector eslint:Security\" runs rules associated only with the \"eslint\" engine that have the Security tag.  The flag \"--rule-selector eslint:Security:3\" flag runs the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the --rule-selector flag multiple times, such as \"--rule-selector eslint:Recommended --rule-selector retire-js:3\".\n\nRun `<%= config.bin %> code-analyzer rules --rule-selector all` to see the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
+          "name": "rule-selector",
+          "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
+          "default": [
+            "Recommended"
+          ],
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "severity-threshold": {
+          "char": "t",
+          "description": "You can specify either a number (2) or its equivalent string (\"High\").",
+          "name": "severity-threshold",
+          "summary": "Severity level of a found violation that must be met or exceeded to cause this command to fail with a non-zero exit code.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "view": {
+          "char": "v",
+          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information.\n\nIf you specify neither --view nor --output-file, then the default table view is shown. If you specify --output-file but not --view, only summary information is shown.",
+          "name": "view",
+          "summary": "Format to display the command results in the terminal.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "detail",
+            "table"
+          ],
+          "type": "option"
+        },
+        "output-file": {
+          "char": "f",
+          "description": "If you don't specify this flag, the command outputs the results in the terminal. Use this flag to print the results to a file; the format of the results depends on the extension you provide. For example, \"--output-file results.csv\" creates a comma-separated values file. You can specify one of these extensions:\n\n- .csv\n- .html or .htm\n- .json\n- .sarif or .sarif.json\n- .xml\n\nTo output the results to multiple files, specify this flag multiple times.  For example: \"--output-file ./out/results.json --output-file ./out/report.html\" creates a JSON results file and an HTML file in the \"./out\" folder.",
+          "name": "output-file",
+          "summary": "Output file that contains the analysis results. The file format depends on the extension you specify, such as .csv, .html, .xml, and so on.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "config-file": {
+          "char": "c",
+          "description": "Code Analyzer has an internal default configuration for its rule and engine properties. If you want to override these defaults, you can create a Code Analyzer configuration file.\n\nWe recommend that you name your Code Analyzer configuration file \"code-analyzer.yml\" or \"code-analyzer.yaml\" and put it at the root of your workspace. You then don't need to use this flag when you run the `<%= command.id %>` command from the root of your workspace, because it automatically looks for either file in the current folder, and if found, applies its rule overrides and engine settings. If you want to name the file something else, or put it in an alternative folder, then you must specify this flag.\n\nTo help you get started, use the `code-analyzer config` command to create your first Code Analyzer configuration file. With it, you can change the severity of an existing rule, change a rule's tags, and so on. Then use this flag to specify the file so that the command takes your customizations into account.",
+          "name": "config-file",
+          "summary": "Path to the configuration file used to customize the engines and rules.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "code-analyzer:run",
+      "pluginAlias": "@salesforce/plugin-code-analyzer",
+      "pluginName": "@salesforce/plugin-code-analyzer",
+      "pluginType": "jit",
+      "state": "Beta",
+      "strict": true,
+      "summary": "Analyze your code with a selection of rules to ensure good coding practices.",
+      "enableJsonFlag": false,
+      "SF_ENV": "SF_ENV",
+      "isESM": false,
+      "relativePath": [
+        "lib",
+        "commands",
+        "code-analyzer",
+        "run.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "code-analyzer:run",
+        "run:code-analyzer"
+      ]
+    },
     "cmdt:generate:field": {
       "aliases": [
         "force:cmdt:field:create",
@@ -5370,5 +5660,5 @@
       ]
     }
   },
-  "version": "2.73.5"
+  "version": "2.73.6"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.73.5",
+  "version": "2.73.6",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
@@ -75,6 +75,7 @@
       "@salesforce/plugin-user"
     ],
     "jitPlugins": {
+      "@salesforce/plugin-code-analyzer": "5.0.0-beta.0",
       "@salesforce/plugin-custom-metadata": "3.3.41",
       "@salesforce/plugin-community": "3.3.8",
       "@salesforce/plugin-dev": "2.5.1",
@@ -165,7 +166,7 @@
     "@salesforce/plugin-info": "3.4.32",
     "@salesforce/plugin-limits": "3.3.44",
     "@salesforce/plugin-marketplace": "1.3.7",
-    "@salesforce/plugin-org": "5.2.17",
+    "@salesforce/plugin-org": "5.2.18",
     "@salesforce/plugin-packaging": "2.9.12",
     "@salesforce/plugin-schema": "3.3.46",
     "@salesforce/plugin-settings": "2.4.10",