{"version":"2.1.246","anchor":"fewer-false-unpack-failed-bundle-rejections","canonical_anchor":"fewer-false-unpack-failed-bundle-rejections","heading":"Fewer false \"unpack_failed\" bundle rejections","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/fewer-false-unpack-failed-bundle-rejections","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Fewer false \"unpack_failed\" bundle rejections\n\nRepos with boundary commits are no longer wrongly rejected as unpackable when uploading.\n\n**What**\n\nWhen verifying a git bundle, if the object walk reports the pack holds objects the commit range does not name, Claude Code now retries the walk with `--objects-edge-aggressive` before calling the bundle unpackable. Repos with boundary commits are no longer refused for this reason.\n\n**Details**\n\n- The retry ignores boundary lines, which begin with `-`.\n- Only if the retry still disagrees is the bundle declared unpackable.\n\n**Evidence**\n\n`--objects-edge-aggressive`\n\n- Area: Cloud Sessions\n- Names: `--objects-edge-aggressive`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}