-
Notifications
You must be signed in to change notification settings - Fork 1.7k
-
This is a servicing release build of Windows Package Manager v1.12. If you find any bugs or problems, please help us out by filing an issue
New in v1.12
- MCP server available; run
winget mcpfor assistance on configuring your client. - App Installer now uses WinUI 3. The package dependency on WinUI 2 has been replaced by a dependency on the Windows App Runtime 1.8.
- Manifest schema and validation updated to v1.12. This version update adds
Fontas anInstallerTypeandNestedInstallerType. - Font Install, Uninstall, and a winget-fonts source have been added and are non-experimental.
Bug Fixes
- Manifest validation no longer fails using
UTF-8 BOMencoding when the schema header is on the first line - Upgrading a portable package with dev mode disabled will no longer remove the package from the PATH variable.
- Fixed source open failure when there were multiple sources but less than two non-explicit sources.
- Fixed an issue where App Installer would not update its progress.
- Fixed an issue with opening packages that require elevation in App Installer.
- Fixed an issue that prevented App Installer from launching on older OS builds when the Windows App Runtime is missing.
- Fixed an issue that blocked activation of MSIX apps with
OnLaunchupdates in older OS builds. - Fixed an issue where App Installer would fail to open a file if the calling process exited too soon.
Font Support
Font Install and Uninstall via manifest and package source for user and machine scopes has been added.
A sample Font manifest can be found at:
https://github.com/microsoft/winget-pkgs/tree/master/fonts/m/Microsoft/FluentFonts/1.0.0.0
At this time install and removal of fonts is only supported for fonts installed via WinGet Package.
Fonts must either be the Installer or a .zip archive of NestedInstaller fonts.
A new explicit source for fonts has been added "winget-font".
winget search font -s winget-font
This source is not yet accepting public submissions at this time.
Experimental Features
- Experimental support still exists for the 'font' command.
Experimental support for Fonts
The following snippet enables experimental support for fonts via winget settings. The winget font list command will list installed font families and the number of installed font faces.
{
"$schema" "https://aka.ms/winget-settings.schema.json",
"experimentalFeatures": {
"Font": true
}
}The font 'list' command has been updated with a new '--details' feature for an alternate view of the installed fonts.
What's Changed
- Make Repair-WGPM a COM-aware cmdlet and rework version retrieval (CP to 1.12) by @JohnMcPMS in Make Repair-WGPM a COM-aware cmdlet and rework version retrieval (CP to 1.12) #5858
- Unregister signal handler (CP to 1.12) by @JohnMcPMS in Unregister signal handler (CP to 1.12) #5862
- Support associating export units with packages in subdirectories (1.12) by @JohnMcPMS in Support associating export units with packages in subdirectories (1.12) #5866
Full Changelog: v1.12.350...v1.12.440
This discussion was created from the release Windows Package Manager 1.12.440.
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 4 -
😄 2 -
🎉 3 -
❤️ 2 -
🚀 2
Replies: 1 comment 2 replies
-
Under New in v1.12 it mentions
Font Install, Uninstall, and a winget-fonts source have been added and are non-experimental.
But under Experimental Features, fonts is mentioned like this
Experimental support for Fonts
The following snippet enables experimental support for fonts via winget settings. The winget font list command will list installed font families and the number of installed font faces.
{
"$schema" "https://aka.ms/winget-settings.schema.json",
"experimentalFeatures": {
"fonts": true
}
}
Are there some parts that are still experimental?
Beta Was this translation helpful? Give feedback.
All reactions
-
The functionality for font install, remove, and the like, is not experimental. Fonts are treated as new type of installer, so you use the same commands as you would for other packages. For example, winget install <something>.
The part that is still experimental is an additional font command. That is, winget font <something>. That was left over from a previous design where fonts would be treated differently from other packages. It is experimental because it is not clear what purpose it would have now, or if we should do away with it.
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
The implementation of the experimental font feature doesn't match the settings documentation (we're going to update it).
@Frulfump, try:
"Font": true
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1