Update git command executions - #143
Merged
Merged
Conversation
Contributor
mwolting
approved these changes
Sep 15, 2026
This was referenced Sep 15, 2026
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.
Release commit metadata could execute shell commands during baseline and rollback checks (SEC-1502).
Replace all runtime
execSynccalls withexecFileSyncargument arrays, reject malformed SHAs before Git checks or fetching, and add option separators to prevent refs and remote names from being interpreted as Git options.Extend
git.test.tswith regression coverage for shell payloads, poisoned release metadata, fetch option injection, and valid SHAs.Validation: full suite passed (460 tests), followed by 130 affected tests after the final ref hardening; typecheck, lint, formatting, and build passed.
Towards SEC-1502