fix: preserve PowerShell installer encoding - #1
Draft
Ahho0927 wants to merge 2 commits into
Draft
Conversation
5 tasks
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
1 participant
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.
What changed
scripts/install.ps1with a UTF-8 BOM for Windows PowerShell 5.1.Root cause
Windows PowerShell 5.1 interpreted the BOM-less UTF-8 installer using the legacy system code page. Korean messages became mojibake and caused parser errors during the Windows installer integration test.
Impact
The Windows installer remains readable and executable in both Windows PowerShell 5.1 and PowerShell 7. The Windows CI test remains enabled so platform-specific regressions are detected.
Validation
go test ./...go test -race ./...go vet ./...git diff --checkEF BB BFat the beginning ofscripts/install.ps1.