{"version":"2.1.242","anchor":"uploaded-git-bundles-are-checked-against-your-own-object-sto","canonical_anchor":"uploaded-git-bundles-are-checked-against-your-own-object-sto","heading":"Uploaded git bundles are checked against your own object store","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/uploaded-git-bundles-are-checked-against-your-own-object-sto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Uploaded git bundles are checked against your own object store\n\nUploaded git bundles are verified against your own checkout before being sent.\n\n**What**\n\nAfter building a bundle, Claude Code now confirms every commit it references really exists in this checkout, so a bundle assembled against some other object store is rejected rather than uploaded.\n\n**Details**\n\n- Bundle heads are piped through `cat-file --batch-check`; a mismatch fails with reason `git_dir_tampered`.\n- Companion checks cover refs that were missing, ambiguous, or changed while the bundle was being built, each with its own remediation text.\n- Only on the hardened upload path; skipped when the legacy path is in use.\n\n**Evidence**\n\n`at commits this checkout's own object store does not hold: another object store stood in while the bundle was made.`\n\n- Area: Cloud Sessions\n- Names: `--batch`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}