fix: remove Repomix shell execution (0.12.4) - #27
Merged
Conversation
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.
Repomix probing and packing previously ran through cmd/npx, allowing environment-derived paths to be interpreted by a shell. Launch the installed JavaScript bin directly through Node with separate arguments; preserve builtin fallback and disabled behavior. Document the explicit JS entry override and the removal of npx-cache/shell-wrapper discovery.
Validation: complete local check passed (307 pass, 1 existing optional skip), including production stdio and delivery verification. Real child-process fixtures cover special-character paths/argv, missing overrides, local package discovery, timeout/cancellation and PID exit. Replace two npx-timing-dependent tests and one growing-checkout-dependent test with fixed fixtures without relaxing production limits.
main protection is now enabled with Node 22/24 and three CodeQL checks. Verify exact-head CI before merging and alert #1 afterward; a successful scan alone does not establish alert closure. Real Serena integration revealed a separate response-envelope compatibility defect and is not claimed as passed here.