{{ message }}
Tags: microsoft/winget-cli
Tags
Fix configuration elevation validation for standard flow (1.29) (#6318) CP of #6307 to 1.29 Technically it wasn't a CP because of the line ending renormalization. You can filter that out using the following method: - Create your CP branch off the target - `git show <HASH> -w > temp.patch` - `git apply -p1 --ignore-whitespace temp.patch` - Or you can combine it into one `git show <HASH> -w | git apply -p1 --ignore-whitespace -` - Commit the changes ## 📖 Description As described in the issue, when using standard configuration flows that have elevated units, the elevated process would not operate properly. This came down to a case sensitive bool conversion that would cause the validation flow to not properly read from the alias file.
Apply latest loc patch (#6262) ###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/microsoft/winget-cli/pull/6262)
Optimize packaged temp ACL handling without weakening ACL repairs (#6171 ) This change reduces the severe slowdown caused by recursive ACL propagation on packaged temp paths while preserving the security behavior that repairs improperly secured directories before use. The fix keeps the existing fail-closed model, but avoids calling `ApplyACL()` when the target directory is already in the exact secure state winget expects.
Improved manifest validations for MSI and Windows Feature names (#6170) CP of #6169 onto main branch. ## Change Adds some additional validation for MSI switches and Windows Feature names: 1. MSI switches are checked during full manifest validation in the same way that they are checked when we attempt to use the MSI APIs rather than msiexec. The API is used for fully all silent installs of MSIs, so we now ensure that those will work (6 total manifests in winget-pkgs were found that needed fixes). 2. Windows Feature names in dependencies are validated to be { alphanumeric, `-`, `_` }. This is done both during full manifest validation and at runtime. A PowerShell script (tools/ManifestValidation/Invoke-ManifestValidation.ps1) is added that will run `wingetdev validate` against a directory recursively and generate a report. There is support for resuming in the middle of the run. This would probably perform much better if it were updated to use the WinGetUtil API, but that can be a future project.
PreviousNext
