Repository navigation
Fix Windows wrapper bootstrap from PowerShell 7 and release 0.3.1 - #1
Merged
Merged
Conversation
IRus
marked this pull request as ready for review
October 18, 2026 00:25
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.
Running ktc-plugins.bat from PowerShell 7 fails before the installer starts because its Windows PowerShell child inherits incompatible module paths and cannot resolve Get-FileHash. Clear PSModulePath inside the existing setlocal scope before starting the bootstrap shell. Prepare patch release 0.3.1 with synchronized CLI, launcher, CI and documentation versions.
The Windows wrapper suite now runs through both cmd.exe and pwsh. Both paths cover cached launches, paths with spaces, argument forwarding, empty-cache downloads, concurrent bootstrap and corrupt-download rejection.
Validation: