Repository navigation
docs: winget package is published - #543
Merged
Merged
Conversation
wslkit.skrog 0.8.0 merged in microsoft/winget-pkgs#436048. Adds winget as an install route, drops the 'on the way' wording, and documents what happens with two installs side by side. Closes #412
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
wslkit.skrog0.8.0 is published on winget (microsoft/winget-pkgs#436048, merged 2026-10-13, publish pipeline succeeded).Changes
winget install wslkit.skrogsits beside the install script and scoop. The two "a winget package is on the way" lines are updated. "What's ahead" now names signing and the MSI.Verified on a real machine
winget install wslkit.skrog, from the published source: hash verified and the alias was created. Through the alias,skrog versionreports 0.8.0.skrog autostart enablewrites the Run entry toWinGet\Packages\…\skrogw.exe, which exists, so the os.Executable() is used to find sibling files, which breaks behind a symlink shim (winget portable) #360 regression is not present.winget install --manifest): it reports 0.10.0, and autostart resolves into the package directory.winget installleft two copies, and plainskrogkept running the script's copy because%LOCALAPPDATA%\Programs\skrogcomes beforeWinGet\Linkson the user PATH. That the install script appends to PATH is fromscripts/install.ps1:170.Not verified on a real install
skrog upgrade --applyrefusing under winget is read from the code (cmd/skrog/upgrade.go:375,internal/upgrade/owner.go) and covered byowner_test.go. It wasn't run through a winget install. The refusal only fires when the app is behind, and on this machine an older winget copy would have meant--applyupgrading the real engine first. That ordering is a follow-up question: under winget,--applyapplies the engine and CLI steps and then refuses the app.Closes #412