KEMBAR78
Comparing v1.12.240-preview...v1.12.250-preview · microsoft/winget-cli · GitHub
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: microsoft/winget-cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.12.240-preview
Choose a base ref
...
head repository: microsoft/winget-cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.12.250-preview
Choose a head ref
  • 2 commits
  • 9 files changed
  • 1 contributor

Commits on Sep 15, 2025

  1. Add the ARP correlation entry to the context for portable installs (#… 

    …5707)

Fixes #5688

## Issue
We were not recording ARP changes for portable installs, which prevented
the product code from being in the tracking database, which led to
inconclusive correlation results for packages with shared normalized
name+publisher.

## Change
Portable install flow extracts the `AppsAndFeaturesEntry` for the
install and puts it into the `CorrelatedAppsAndFeaturesEntries` context
item.
    @JohnMcPMS
    JohnMcPMS authored Sep 15, 2025
    Configuration menu
    Copy the full SHA
    9ac99d2 View commit details
    Browse the repository at this point in the history

  2. Fix two unrelated version issues (#5719) 

    Fixes #4928
Fixes providing "1" for the version when the version is actually "1.0"
and the like (there is probably an issue filed but I didn't find it
after a quick search).

## Issues
Due to SQLite helpfully not being picky about data types, the packages
table in the v2 index was using INT64 for every column, when in reality
they should mostly by strings (TEXT). When the version was parsable as a
number, it would drop unnecessary portions (trailing 0s).

New code in the v2 index and the composite package changes were using
string comparison instead of `Version`, requiring an exact string match
rather than `Version` equality.

## Changes
Use the data type that we already had set up rather than always INT64.
This will require a service update to actually fix anything (but doesn't
require a client update).

Use `Version` comparisons rather than string in the v2 index and
composite package version selection.
    @JohnMcPMS
    JohnMcPMS authored Sep 15, 2025
    Configuration menu
    Copy the full SHA
    fc36248 View commit details
    Browse the repository at this point in the history
Loading