brew.sh: avoid here-string for sandbox compatibility #21175
Merged
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.
Following up on #21157, which made
shellenv.shsandbox-compatible by usinglsofinstead ofps, this change addresses another sandbox issue inbrew.sh.The here-string syntax triggers a warning:
This occurs because here-strings (
<<<) internally create temporary files, which many sandboxes restrict for security reasons.Changes
Replaces the here-string version parsing with IFS-based word splitting:
This produces identical results without requiring temp file creation.
Testing
Verified that
brew shellenvruns without warnings when executed under sandbox-runtime and that version parsing continues to work correctly.I used https://github.com/anthropic-experimental/sandbox-runtime below, which is what Claude Code uses internally for its sandboxing. It uses Seatbelt on macOS.
Before
After
References