Windows Package Manager 1.28.100 Preview released
Microsoft has recently released a new preview build of Winget, specifically version 1.28.100, designed for individuals eager to actively test the upcoming changes.
One thing caught my eye right away: the version number for winget itself was updated from 0.x to a 1.x format this time, aligning it properly with its core package manager counterpart.
A new option related to logs is also on board. For users generating lots of log data, maybe you're tracking things closely? There's now a way to control how big those files are allowed to get. That could be handy.
Then there's this experimental feature called 'sourceEdit' showing up for the first time. It adds an interesting twist to working with sources using that winget source command. The new 'edit' subcommand basically lets you switch between having a source defined explicitly and letting it follow implicit rules at will. For instance, imagine something like the winget-font source, normally explicit in older setups, now being part of the system by default via an implicit definition. You can adjust this behavior with commands.
To get to grips with 'sourceEdit,' you'll need to flip a switch in your settings. It requires adding a section "experimentalFeatures": { "sourceEdit": true } somewhere appropriate (likely settings.json). Once 'sourceEdit' is active, using the command 'winget source edit winget-font' provides a straightforward command-line interface to modify both the explicit and implicit states.
Digging into specific bug fixes, it's looking healthier this time around. Portable Packages now seem smarter about directory separators; they handle both forward and backward slashes consistently without fuss, which is something that was likely causing friction before.
Also addressed is how the Winget Configuration Test handles the initial detail output when combined with the --suppress-initial-details flag. That flag should work as expected now, meaning you don't accidentally need to use --accept-configuration-agreements just because a flag didn't behave properly earlier. It seems smoother overall.
Other notable fixes touch on an experimental font feature's own properties; they got aligned better than before, which makes sense if it was misclassified previously. And there was one tricky JSON issue fixed deep within the commit history that probably wasn't causing problems but still needed sorting.
The same goes for COM module validation tests; they've received some attention and should be more reliable now. Package paths also benefit from this fix regarding directory separators, so there is less chance of unexpected failures due to slashes again.
Beyond these specific improvements, developers have been diligently refining the Windows Package Manager in other areas as well. They've made background improvements focused on making things more stable generally and ensuring features function as intended consistently across the board. The change includes adjustments like tweaking sleep times for background threads (to prevent early termination) or modifying build processes (making everything just a bit neater). It's that kind of stuff you probably don't hear much about, but it helps keep the whole thing running properly.
So, while there are some nifty new features peeking out from behind the preview label and solid bug fixes being delivered, this update also involves important foundational work happening underneath the surface.
Release Windows Package Manager 1.28.100-preview
This is a preview build of WinGet for those interested in trying out upcoming features and fixes. While it has had some use and should be free of major issues, it may have bugs or usability problem...
Release Windows Package Manager 1.28.100-preview ยท microsoft/winget-cli
