Skip to content

Conversation

@wesm
Copy link
Collaborator

@wesm wesm commented Jan 31, 2026

Summary

  • Add -Encoding UTF8 to Set-Content in pwdCmd to avoid UTF-16LE on Windows PowerShell 5.1
  • Use exact path comparison on Unix, EqualFold only on Windows
  • Add t.Cleanup safety net for logger restoration in log capture tests
  • Fix stale shellEscape doc comment to reflect single-quote behavior

Test plan

  • CI passes on all platforms (Ubuntu, macOS, Windows)

🤖 Generated with Claude Code

wesm and others added 2 commits January 31, 2026 17:42
- Add -Encoding UTF8 to Set-Content in pwdCmd for Windows PS 5.1
- Use exact path comparison on Unix, case-insensitive only on Windows
- Add t.Cleanup safety net for logger restoration in log tests
- Fix stale shellEscape doc comment (now single quotes on all platforms)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Set-Content -Encoding UTF8 writes a BOM on PS 5.1. Use
[IO.File]::WriteAllText which writes UTF-8 without BOM.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@wesm wesm merged commit 9eca728 into main Jan 31, 2026
7 checks passed
@wesm wesm deleted the hooks-refinements branch January 31, 2026 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants