microsoft / microsoft/winget-pkgs

[New Feature]: Enable verbose logs in installation validation pipeline

Open
#344,363 4 comments 5 reactions 0 assignees View on GitHub
Area-Validation-Pipeline Issue-Feature
Dominant language
No language data
Stars
11.1k
Forks
9.7k
PR merge metrics
PR metrics pending

Description

### Description of the new feature/enhancement

Heavily inspired by https://github.com/microsoft/winget-pkgs/issues/341319#issuecomment-3940299852.
I think it would be better if the logs from the pipeline are verbose instead, it would avoid some confusion sometimes with packages that had dependencies on them.

For instance, instead of this:
```
2026-02-03 08:27:25.982 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.arm64 with version 14.50.35719.0
2026-02-03 08:27:25.983 [CLI ] Terminating context: 0x8a150104 at C:__w\1\s\external\pkg\src\AppInstallerCLICore\Workflows\DependenciesFlow.cpp:129
```

This is better:
```
2026-03-02 16:51:12.883 [CLI ] Architecture Comparator created with allowed architectures: [Arm64]
2026-03-02 16:51:12.883 [CLI ] Starting installer selection.
2026-03-02 16:51:12.883 [CLI ] Installer [Arm64,burn,Machine,] not applicable: Installer locale does not match required locale: Required locales: [en-US] Or does not satisfy compatible match for Preferred Locales: [en-US, en-ID, id]
2026-03-02 16:51:12.883 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.arm64 with version 14.50.35719.0
2026-03-02 16:51:12.884 [CLI ] Terminating context: 0x8a150104 at C:\__w\1\s\external\pkg\src\AppInstallerCLICore\Workflows\DependenciesFlow.cpp:129
```

### Proposed technical implementation details (optional)

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing the installation validation pipeline and where its current log verbosity is configured. Compare the existing output with the proposed examples; done should mean dependency and installer-selection details are emitted clearly during validation.

Written by the indexing model from the issue text.

Assessment

Domain
cli, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.