[Slai.life (huong8373tt-beep)]

Summary

Resolves #6516.

winget upgrade --all --scope user can list an available update, then skip it when no compatible user-scope installer exists. The single-package flow explains that outcome, but the --all flow previously omitted it.

This change counts APPINSTALLER_CLI_ERROR_UPDATE_NOT_APPLICABLE results in UpdateAllApplicable() and reports a concise summary after processing available updates.

Validation

• Added UpdateFlow_UpdateAll_ReportsNotApplicable, using an installed EXE package whose newer manifest contains only a machine-scope installer while --scope user is requested.
• Added the 1.31 release-note fragment.
• git diff --check passed.
• Merge-ReleaseNotes.ps1 -Version 1.31 passed.
• Project XML and the new YAML fixture parsed successfully.
• A local C++ test build was attempted, but dependency acquisition in the local environment prevented the test binary from being produced; the repository CI remains the full build-and-test authority.

AI assistance disclosure

Slai Agent Runtime performed the investigation, implementation, and test execution. The account owner authorized this contribution and is responsible for its content.

Microsoft Reviewers: Open in CodeFlow

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Slai.life (huong8373tt-beep)]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 6637 in repo microsoft/winget-cli

[Copilot]

🟡 Changes recommended

The added user-scope argument breaks an existing upgrade success-path test, and the skipped-upgrade counter incorrectly includes already-current and pinned packages.

2 open issues

• Remove user scope from the existing EXE upgrade test · New
• Count only installer-inapplicability failures as skipped upgrades · New

What changed in this PR

This PR addresses #6516 by adding a summary for upgrades skipped as not applicable during winget upgrade --all, extending reporting previously available only for single-package upgrades.

Changes:

• Counts not-applicable results and adds an English summary resource.
• Adds a scope-mismatch regression test, supporting fixture, and test-project registration.
• Adds a 1.31 release-note fragment describing the new output.

File	Description
src/​AppInstallerCLITests/​WorkflowCommon.h	Declares the new test-source result.
src/​AppInstallerCLITests/​WorkflowCommon.cpp	Defines a package with a machine-scope upgrade.
src/​AppInstallerCLITests/​UpdateFlow.cpp	Adds summary coverage and modifies the existing success test’s scope.
src/​AppInstallerCLITests/​TestData/​UpdateFlowTest_Exe_MachineScope.yaml	Supplies the machine-only EXE upgrade fixture.
src/​AppInstallerCLITests/​AppInstallerCLITests.vcxproj.filters	Groups the new fixture under test data.
src/​AppInstallerCLITests/​AppInstallerCLITests.vcxproj	Includes the fixture in test deployment.
src/​AppInstallerCLIPackage/​Shared/​Strings/​en-us/​winget.resw	Adds the skipped-upgrade summary text.
src/​AppInstallerCLICore/​Workflows/​UpdateFlow.cpp	Counts and reports not-applicable upgrade results.
src/​AppInstallerCLICore/​Resources.h	Exposes the new summary resource identifier.
doc/​release-notes/​1.31/​6516-upgrade-all-skip-reason.md	Documents the user-visible reporting change.

_{Review effort: Balanced}

[JohnMcPMS]

Suggested change

	if (updateContext.Contains(Execution::Data::InstallerInapplicable))
	if (updateContext.Contains(Execution::Data::InstallerInapplicable) && updateContext.Get(Execution::Data::InstallerInapplicable))

If it is going to be a bool, there are two values.

[Copilot]

🟡 Changes recommended

A blocked version can leave packagePinned true and suppress both summaries when another newer version passes pin evaluation but has no applicable installer; this case needs corrected tracking and a regression test.

1 open issue

• Report pin skips when another eligible version lacks an installer · New

2 resolved since last review

• Remove user scope from the existing EXE upgrade test
• Count only installer-inapplicability failures as skipped upgrades

_{Review effort: Balanced}

[Slai.life (huong8373tt-beep)]

Addressed the mixed pinned/inapplicable version case from review. The workflow now tracks whether a newer version passed pin evaluation and whether installer selection failed independently of packagePinned, and the regression test covers a pinned 2.0 version plus an allowed 1.1 version with only a machine-scope installer. Also normalized the existing release-note/test-data files to end with a newline. Commit: 18fc238. Local Windows build reached the repository C++/WinRT/vcpkg stage but was blocked by the shared vcpkg filesystem lock; no code assertion failure was observed.

[Slai.life (huong8373tt-beep)]

I am rechecking the latest Copilot comments against the current head before making any follow-up changes. I will address only confirmed issues and report the Windows validation status separately.