{"version":"2.1.301","anchor":"git-fetch-hard-cap-failure-can-now-throw-a-distinct-permanen","canonical_anchor":"git-fetch-hard-cap-failure-can-now-throw-a-distinct-permanen","heading":"Permanent git fetch failures are now told apart from temporary ones","tier":"internal","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/git-fetch-hard-cap-failure-can-now-throw-a-distinct-permanen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Permanent git fetch failures are now told apart from temporary ones\n\nWhen git fetch gives up after its retry limit because a ref does not exist, it now raises a separate kind of error\n\n**What**\n\nIn BYOC environments, Claude Code retries `git fetch` several times before it gives up. When it reaches the overall retry limit and the failure is a permanent one, such as a branch or ref that does not exist, it now raises a distinct kind of error. Before, every such failure raised the same general error. The message text is unchanged.\n\n**Why**\n\nA permanent failure such as a missing ref will not fix itself with more attempts. Code that handles these errors can now tell those cases apart from failures that might succeed later.\n\n- Area: Self-Hosted Runners\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}