fix: use execFile to bypass shell command resolution-W-23662030 - #897
Merged
Conversation
|
Git2Gus App is installed but the |
WillieRuemmele
approved these changes
Aug 4, 2026
Contributor
QA Notes✅ : verified on Sorida's windows VM as working with fix |
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
2 participants
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.
Summary
child_process.exec()withchild_process.execFile()when invoking npmexecFiledoes not spawn a shell, preventing unintended command resolution from the working directory on WindowsTest plan
sf version --verboseworks correctly on Windows and macOS@W-23662030@