Handle shell startup output in installed package JSON - #157
Draft
joseph1020 wants to merge 1 commit into
Draft
Conversation
MikeMcQuaid
requested changes
Sep 10, 2026
MikeMcQuaid
left a comment
Member
There was a problem hiding this comment.
We will not be merging any community PRs until after Homebrew 7.0.0 is released.
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
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
Allow the Installed repository to decode
brew info --installed --json=v2when interactive-shell startup output appears before Homebrew's JSON.
This was reproduced with iTerm2 shell integration emitting OSC 1337 sequences
before an otherwise valid Homebrew JSON payload.
Changes
Testing
git diff --check.PR checklist
the decoding boundary, and drafting the regression and implementation.
I manually reproduced the issue and reviewed the final diff.