You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,13 +20,14 @@ The client is distributed within the [App Installer](https://apps.microsoft.com/
20
20
21
21
### Development Releases
22
22
23
-
There are two methods to get development releases:
23
+
There are a few methods to get development releases:
24
24
25
25
* Install a [Windows 10 or Windows 11 Insider](https://insider.windows.com/) build.
26
-
* Join the Windows Package Manager Insider program by [signing up](http://aka.ms/winget-InsiderProgram).
26
+
* Manually update using a development build from our [Releases](https://github.com/microsoft/winget-cli/releases) page.
27
+
* Use the `Repair-WinGetPackageManager` cmdlet from the [Microsoft.WinGet.Client](https://www.powershellgallery.com/packages/Microsoft.WinGet.Client/) PowerShell module and use the `-IncludePrerelease` parameter.
27
28
28
29
> [!NOTE]
29
-
> It may take a few days to get the updated App Installer after you receive e-mail confirmation from joining the Windows Package Manager Insider program. If you decide to install the latest release from GitHub, and you have successfully joined the insider program, you will receive updates when the next development release has been published in the Microsoft Store.
30
+
> If you decide to install the latest release from GitHub, and you have successfully joined the insider program, you will receive updates when the next development release has been published in the Microsoft Store.
30
31
31
32
Once you have received the updated App Installer from the Microsoft Store you should be able to execute `winget features` to see experimental features. Some users have reported [issues](https://github.com/microsoft/winget-cli/issues/210) with the client not being on their PATH.
32
33
@@ -119,3 +120,4 @@ In short, to opt out, do one of the following:
119
120
**Windows 10**: Go to `Start`, then select `Settings` > `Privacy` > `Diagnostics & feedback`, and select `Required diagnostic data`.
120
121
121
122
See the [privacy statement](PRIVACY.md) for more details.
New feature that adds an 'edit' subcommand to the 'source' command. This can be used to set an explicit source to be implicit and vice-versa. For example, with this feature you can make the 'winget-font' source an implicit source instead of explicit source.
5
+
6
+
To enable this feature, add the 'sourceEdit' experimental feature to your settings.
7
+
```
8
+
"experimentalFeatures": {
9
+
"sourceEdit": true
10
+
},
11
+
```
12
+
To use the feature, try `winget source edit winget-font` to set the Explicit state to the default.
13
+
3
14
<!-- Nothing yet! -->
4
15
5
16
## Bug Fixes
6
17
* Portable Packages now use the correct directory separators regardless of which convention is used in the manifest
18
+
*`--suppress-initial-details` now works with `winget configure test`
19
+
*`--suppress-initial-details` no longer requires `--accept-configuration-agreements`
Copy file name to clipboardExpand all lines: doc/Settings.md
+39Lines changed: 39 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -286,6 +286,35 @@ In addition, there are special values that cover multiple channels. `default` i
286
286
},
287
287
```
288
288
289
+
### file
290
+
291
+
The `file` settings control the log files generated by winget during operation. These settings apply to the automatic cleanup that happens whenever a Windows Package Manager process is run.
292
+
They only apply to the default log location, which contains winget logs, AppInstaller logs (the MSIX install UI), and is the default location where installer logs are placed.
293
+
The automatic cleanup happens at the beginning of the process, so the log file(s) generated by the current process will not be considered in the limits.
294
+
295
+
|Setting|Description|Default|Note|
296
+
|---|---|---|---|
297
+
|`ageLimitInDays`|The maximum age, in days, of files in the log directory; older files are deleted.|7 (days)|Set to 0 to disable this limit.|
298
+
|`totalSizeLimitInMB`|The maximum size, in megabytes, of all files in the log directory; the oldest files are deleted first.|128 (MB)|Set to 0 to disable this limit.|
299
+
|`countLimit`|The maximum number of files in the log directory; the oldest files are deleted first.|0|Set to 0 (the default) to disable this limit.|
300
+
301
+
These settings apply to the log files that winget writes, only as they are being written. They do not apply to files written by installers or the AppInstaller UI.
302
+
303
+
|Setting|Description|Default|Note|
304
+
|---|---|---|---|
305
+
|`individualSizeLimitInMB`|The maximum size, in megabytes, of an individual log file. If a file would exceed this limit, the logs will wrap. Note that this limit is approximate and the actual files may exceed it by a few bytes.|16 (MB)|Set to 0 to disable this limit.|
306
+
307
+
```json
308
+
"logging": {
309
+
"file": {
310
+
"ageLimitInDays": 7,
311
+
"totalSizeLimitInMB": 128,
312
+
"countLimit": 0,
313
+
"individualSizeLimitInMB": 16,
314
+
}
315
+
},
316
+
```
317
+
289
318
## Network
290
319
291
320
The `network` settings influence how winget uses the network to retrieve packages and metadata.
@@ -364,3 +393,13 @@ This feature enables support for fonts via `winget settings`. The `winget font l
364
393
"fonts": true
365
394
},
366
395
```
396
+
397
+
### sourceEdit
398
+
399
+
This feature enables support for additional source command improvements via `winget settings`. The `winget source edit` command will become available with this feature.
0 commit comments