v1.1.0

Scout for WinGet

Scout for WinGet manages real Windows packages. Install, upgrade, uninstall, and repair actions change your package state. See the README for setup and usage.

What's new in 1.1.0

Scout 1.1.0 makes batch actions easier to follow, adds useful run and backend
diagnostics, and keeps every install, upgrade, and retry behind a review or
confirmation. These changes include all fixes merged since v1.0.3.

Clearer batch actions and progress

• Mark packages with Space or toggle all visible rows with a. In Search,
  i or B reviews marked installs; in Upgrades, u or U reviews marked
  upgrades. Menus put the selected plan first and offer a separate action for
  the highlighted package.
• Headings show visible/total results and selected/hidden counts. Hidden marks
  from filters, source changes, or earlier searches stay in the plan. Escape
  clears all marks after input and pending-work cancellation take priority.
• Reviews show ready and skipped items, keep visible packages in their current
  order, and require an explicit Install (N) or Upgrade (N) approval.
  Enter or double-click inspects the highlighted request without executing it.
• Status and per-package progress have a dedicated footer row. Inventory refresh
  begins when a batch finishes, while its results are open. Successful packages
  are deselected; failed or cancelled ones remain marked.

Run history, diagnostics, and reviewed retries

• L opens the 20 most recent runs. Package details include timing, source,
  versions, requested options, backend, CLI exit codes, and bounded diagnostic
  output. Copy the report or save it as text or JSON.
• Retry package uses the highlighted result; Retry unfinished (N) covers
  retryable failures, cancellations, and skipped requests in interrupted batches.
  Each retry rechecks the original package/source and relevant inventory, version,
  and pin state, then requires a fresh review. Successful packages are not repeated
  by Retry unfinished. Older entries without a recorded request cannot be retried.
• D opens backend and source diagnostics, including version, process
  architecture, capabilities, COM fallback reason, and the last inventory error.
  Read-only source queries distinguish empty results from failures. Reports can be
  refreshed, copied, or saved while another workflow is running.

More predictable controls and options

• Contextual actions are available with m, Shift+F10, or a row's right-click
  menu. They reflect the active tab, backend capabilities, and known pin state.
• Advanced installs explain defaults versus overrides for scope, mode,
  architecture, and custom arguments. Review fetches an installer preview
  before final confirmation. Known scope/architecture conflicts block execution;
  missing previews are stated explicitly.
• Compact tables prioritize names and versions. Full IDs and sources remain in
  Details, and the title shows the active sort even when its column is hidden.
  Sorting, themes, and pin filters preserve the highlighted package when possible.
• Dialog buttons fit without overlapping. Help supports keyboard scrolling;
  blank manual versions receive inline guidance; saved sets start on the first
  row; Ctrl+Q exits through nested dialogs.
• Abandoned checks release the next workflow immediately even if a backend ignores
  cancellation. Late responses cannot open stale reviews or overwrite a new check.
  Delayed progress from an earlier batch item cannot replace the current item.
• Mock sessions use separate local history and settings, disable task scheduling,
  and update their sample inventory after successful upgrades.

See the usage guide for instructions and the
architecture guide for implementation boundaries. These changes
were merged in #54,
#55, and
#56, with regression coverage for
batch outcomes, cancellation and late responses, source identity, dialog controls,
and compact layouts.

Native ARM64 COM installs remain a known limitation; use the CLI backend for
affected operations. Read-only COM preview checks do not validate actual installs.

Downloads

• Portable ZIP (wingetscout-<version>-win-<architecture>.zip): the complete COM build. Extract the folder and run wingetscout.exe.
• Standalone EXE (wingetscout-<architecture>.exe): uses the WinGet CLI backend because its COM companion files are not included.
• SHA256SUMS-*.txt: checksums for each architecture's files.

Portable downloads are currently unsigned. Compare the SHA-256 checksum before running a downloaded file. Build provenance attestations can be checked with gh attestation verify <file> -R harder/wingetscout.

What's Changed

• Announce published v1.0.3 and refresh package links by @harder in #52
• Add reviewed retries, run diagnostics, selection counts, and contextual actions by @harder in #54
• Add backend diagnostics, report exports, and clearer install options by @harder in #55
• Clarify batch actions, progress, retries, and terminal UI workflows by @harder in #56
• Prepare v1.1.0 with updated guides, website, and demos by @harder in #57

Full Changelog: v1.0.3...v1.1.0