-
Notifications
You must be signed in to change notification settings - Fork 3
feat: add Express API changelog generation #319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,2 +1,3 @@ | ||
| * @BitGo/developer-experience | ||
| api.yaml @BitGo/developer-experience @BitGo/technical-writers | ||
| express-api.yaml @BitGo/developer-experience @BitGo/technical-writers |
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
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
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
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.
Check warning
Code scanning / CodeQL
Shell command built from environment values Medium test
Copilot Autofix
AI 3 months ago
In general, the best way to fix this kind of issue is to avoid building a single shell command string that is interpreted by a shell. Instead, call the program directly and pass arguments as an array to
execFileSync/spawnor use the argument-array form ofexecSync, so the Node runtime handles argument escaping and no shell interpretation occurs.For this specific test, we should change the vulnerable
execSynccall on line 53 to use the options form:execSync(command, options)withshell: falseandargsrepresented explicitly. Since we already importexecSyncfromchild_process, andexecSyncsupports an array via itsargsinchild_process.execFileSyncbut not inexecSync, the more direct and clearer fix here is to switch this one call toexecFileSync, which takes(file, args[, options])and does not invoke a shell. That keeps behavior the same (runningnode scripts/api-diff.jswith three CLI arguments) while safely handling any special characters in paths.Concretely:
execFileSyncto the destructured import fromchild_processat the top oftests/generate-release.test.js.execSynccall in the "supports custom file paths via CLI args" test with anexecFileSynccall:execFileSync('node', ['scripts/api-diff.js', path.join(...), path.join(...), 'custom-output.md']);.execSync('node scripts/api-diff.js');alone, since it uses only hard-coded literals and is not part of the tainted flow.No new helper methods are needed; just the additional import and the changed call.