{"version":"2.1.300","anchor":"github-pr-status-batch-reply-is-size-capped-and-validated","canonical_anchor":"github-pr-status-batch-reply-is-size-capped-and-validated","heading":"Pull request status survives oversized or malformed replies from GitHub","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/github-pr-status-batch-reply-is-size-capped-and-validated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Pull request status survives oversized or malformed replies from GitHub\n\nFetching pull request status now caps the reply size and checks each entry, so a bad reply no longer breaks the display\n\n**What**\n\nClaude Code can show the status of GitHub pull requests by asking the `gh` command line tool for them in one batch. Before, it read the reply without any checks or size limit. Now:\n\n- The reply has a size cap. If it is too large, Claude Code logs it and keeps showing the last known status.\n\n- Each pull request in the reply is checked for the expected shape. One that is malformed is logged and reported, instead of being used.\n\n**Why**\n\nA reply that is too big or oddly shaped no longer breaks the pull request status display.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}