@salesforce/plugin-info 2.6.40 → 2.6.42-dev.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,6 +2,8 @@
2
2
 
3
3
  [![NPM](https://img.shields.io/npm/v/@salesforce/plugin-info.svg?label=@salesforce/plugin-info)](https://www.npmjs.com/package/@salesforce/plugin-info) [![Downloads/week](https://img.shields.io/npm/dw/@salesforce/plugin-info.svg)](https://npmjs.org/package/@salesforce/plugin-info) [![License](https://img.shields.io/badge/License-BSD%203--Clause-brightgreen.svg)](https://raw.githubusercontent.com/salesforcecli/plugin-info/main/LICENSE.txt)
4
4
 
5
+ # Foo 4
6
+
5
7
  ## Learn about the plugin-info
6
8
 
7
9
  Salesforce CLI plugins are based on the [oclif plugin framework](<(https://oclif.io/docs/introduction.html)>). Read the [plugin developer guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_plugins.meta/sfdx_cli_plugins/cli_plugins_architecture_sf_cli.htm) to learn about Salesforce CLI plugin development.
@@ -81,20 +83,29 @@ sfdx plugins
81
83
 
82
84
  ## `sfdx doctor`
83
85
 
84
- When you run the doctor command without parameters, it first displays a diagnostic overview of your environment. It then writes a detailed diagnosis to a JSON file in the current directory. Use the --outputdir to specify a different directory. To run diagnostic tests on a specific plugin, use the --plugin parameter. If the plugin isn't listening to the doctor, then you get a warning.
86
+ Gather CLI configuration data and run diagnostic tests to discover and report potential problems in your environment.
85
87
 
86
88
  ```
87
89
  USAGE
88
- $ sfdx doctor
90
+ $ sfdx doctor [--json] [-c <value>] [-p <value>] [-d <value>] [-i]
91
+
92
+ FLAGS
93
+ -c, --command=<value> Command to run in debug mode; results are written to a log file.
94
+ -d, --output-dir=<value> Directory to save all created files rather than the current working directory.
95
+ -i, --create-issue Create a new issue on our GitHub repo and attach all diagnostic results.
96
+ -p, --plugin=<value> Specific plugin on which to run diagnostics.
89
97
 
90
- OPTIONS
91
- -c, --command=command
92
- -d, --output-dir=output-dir
93
- -i, --create-issue
94
- -p, --plugin=plugin
95
- --json Format output as json.
98
+ GLOBAL FLAGS
99
+ --json Format output as json.
96
100
 
97
101
  DESCRIPTION
102
+ Gather CLI configuration data and run diagnostic tests to discover and report potential problems in your environment.
103
+
104
+ When you run the doctor command without parameters, it first displays a diagnostic overview of your environment. It
105
+ then writes a detailed diagnosis to a JSON file in the current directory. Use the --outputdir to specify a different
106
+ directory. To run diagnostic tests on a specific plugin, use the --plugin parameter. If the plugin isn't listening to
107
+ the doctor, then you get a warning.
108
+
98
109
  Use the --command parameter to run a specific command in debug mode; the doctor writes both stdout and stderr to
99
110
  \*.log files that you can provide to Salesforce Customer Support or attach to a GitHub issue.
100
111
 
@@ -103,37 +114,57 @@ DESCRIPTION
103
114
 
104
115
  EXAMPLES
105
116
  Run CLI doctor diagnostics:
106
- sfdx doctor
117
+
118
+ $ sfdx doctor
119
+
107
120
  Run CLI doctor diagnostics and the specified command, and write the debug output to a file:
108
- sfdx doctor --command "force:org:list --all"
121
+
122
+ $ sfdx doctor --command "force:org:list --all"
123
+
109
124
  Run CLI doctor diagnostics for a specific plugin:
110
- sfdx doctor --plugin @salesforce/plugin-source
125
+
126
+ $ sfdx doctor --plugin @salesforce/plugin-source
111
127
  ```
112
128
 
113
- _See code: [src/commands/doctor.ts](https://github.com/salesforcecli/plugin-info/blob/v2.3.2-t.0/src/commands/doctor.ts)_
129
+ _See code: [src/commands/doctor.ts](https://github.com/salesforcecli/plugin-info/blob/v2.6.43-dev.0/src/commands/doctor.ts)_
114
130
 
115
131
  ## `sfdx info:releasenotes:display`
116
132
 
133
+ Display Salesforce CLI release notes on the command line.
134
+
117
135
  ```
118
136
  USAGE
119
- $ sfdx info:releasenotes:display
137
+ $ sfdx info:releasenotes:display [--json] [-v <value>]
120
138
 
121
- OPTIONS
122
- -v, --version=version
123
- --json Format output as json.
139
+ FLAGS
140
+ -v, --version=<value> CLI version or tag for which to display release notes.
141
+
142
+ GLOBAL FLAGS
143
+ --json Format output as json.
144
+
145
+ DESCRIPTION
146
+ Display Salesforce CLI release notes on the command line.
147
+
148
+ By default, this command displays release notes for the currently installed CLI version on your computer. Use the
149
+ --version flag to view release notes for a different release.
124
150
 
125
151
  ALIASES
126
152
  $ sfdx whatsnew
127
153
 
128
154
  EXAMPLES
129
155
  Display release notes for the currently installed CLI version:
130
- sfdx info:releasenotes:display stable, stable-rc, latest, latest-rc, rc
156
+
157
+ $ sfdx info:releasenotes:display stable, stable-rc, latest, latest-rc, rc
158
+
131
159
  Display release notes for CLI version 7.120.0:
132
- sfdx info:releasenotes:display --version 7.120.0 stable, stable-rc, latest, latest-rc, rc
160
+
161
+ $ sfdx info:releasenotes:display --version 7.120.0 stable, stable-rc, latest, latest-rc, rc
162
+
133
163
  Display release notes for the CLI version that corresponds to a tag (stable, stable-rc, latest, latest-rc, rc):
134
- sfdx info:releasenotes:display --version latest
164
+
165
+ $ sfdx info:releasenotes:display --version latest
135
166
  ```
136
167
 
137
- _See code: [src/commands/info/releasenotes/display.ts](https://github.com/salesforcecli/plugin-info/blob/v2.3.2-t.0/src/commands/info/releasenotes/display.ts)_
168
+ _See code: [src/commands/info/releasenotes/display.ts](https://github.com/salesforcecli/plugin-info/blob/v2.6.43-dev.0/src/commands/info/releasenotes/display.ts)_
138
169
 
139
170
  <!-- commandsstop -->
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "2.6.40",
2
+ "version": "2.6.42-dev.1",
3
3
  "commands": {
4
4
  "doctor": {
5
5
  "id": "doctor",
package/package.json CHANGED
@@ -1,29 +1,29 @@
1
1
  {
2
2
  "name": "@salesforce/plugin-info",
3
3
  "description": "Plugin for accessing cli info from the command line",
4
- "version": "2.6.40",
4
+ "version": "2.6.42-dev.1",
5
5
  "author": "Salesforce",
6
6
  "bugs": "https://github.com/forcedotcom/cli/issues",
7
7
  "main": "lib/index.js",
8
8
  "dependencies": {
9
- "@oclif/core": "^2.11.10",
10
- "@salesforce/core": "^5.2.0",
9
+ "@oclif/core": "^2.15.0",
10
+ "@salesforce/core": "^5.2.7",
11
11
  "@salesforce/kit": "^3.0.9",
12
- "@salesforce/sf-plugins-core": "^3.1.14",
12
+ "@salesforce/sf-plugins-core": "^3.1.20",
13
13
  "got": "^11.8.6",
14
14
  "marked": "^4.3.0",
15
15
  "marked-terminal": "^4.2.0",
16
16
  "open": "^8.4.2",
17
- "proxy-agent": "^6.3.0",
17
+ "proxy-agent": "^6.3.1",
18
18
  "semver": "^7.5.4",
19
19
  "tslib": "^2"
20
20
  },
21
21
  "devDependencies": {
22
22
  "@oclif/plugin-command-snapshot": "^4.0.14",
23
- "@salesforce/cli-plugins-testkit": "^4.3.0",
23
+ "@salesforce/cli-plugins-testkit": "^4.3.5",
24
24
  "@salesforce/dev-config": "^4.0.1",
25
- "@salesforce/dev-scripts": "^5.7.0",
26
- "@salesforce/plugin-command-reference": "^3.0.25",
25
+ "@salesforce/dev-scripts": "^5.10.0",
26
+ "@salesforce/plugin-command-reference": "^3.0.31",
27
27
  "@salesforce/prettier-config": "^0.0.3",
28
28
  "@salesforce/ts-sinon": "^1.4.14",
29
29
  "@swc/core": "1.3.39",
@@ -34,8 +34,8 @@
34
34
  "@types/sinon-chai": "^3.2.9",
35
35
  "@typescript-eslint/eslint-plugin": "^5.61.0",
36
36
  "@typescript-eslint/parser": "^5.62.0",
37
- "chai": "^4.3.7",
38
- "eslint": "^8.47.0",
37
+ "chai": "^4.3.8",
38
+ "eslint": "^8.49.0",
39
39
  "eslint-config-prettier": "^8.10.0",
40
40
  "eslint-config-salesforce": "^2.0.2",
41
41
  "eslint-config-salesforce-license": "^0.2.0",
@@ -47,7 +47,7 @@
47
47
  "husky": "^7.0.4",
48
48
  "mocha": "^9.1.3",
49
49
  "nyc": "^15.1.0",
50
- "oclif": "^3.11.2",
50
+ "oclif": "^3.14.0",
51
51
  "prettier": "^2.8.8",
52
52
  "pretty-quick": "^3.1.0",
53
53
  "shx": "0.3.4",
@@ -55,7 +55,7 @@
55
55
  "sinon-chai": "^3.7.0",
56
56
  "ts-node": "^10.4.0",
57
57
  "typescript": "^4.9.5",
58
- "wireit": "^0.10.0"
58
+ "wireit": "^0.13.0"
59
59
  },
60
60
  "config": {},
61
61
  "engines": {
@@ -232,7 +232,7 @@
232
232
  }
233
233
  },
234
234
  "sfdx": {
235
- "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-info/2.6.40.crt",
236
- "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-info/2.6.40.sig"
235
+ "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-info/2.6.42-dev.1.crt",
236
+ "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-info/2.6.42-dev.1.sig"
237
237
  }
238
238
  }