{"version":"2.1.269","anchor":"warning-message-broadened-from-git-mount-to-all-of-ccrs-m","canonical_anchor":"warning-message-broadened-from-git-mount-to-all-of-ccrs-m","heading":"Warning message broadened from 'git mount' to all of CCR's mounts including gh writes","tier":"notice","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/warning-message-broadened-from-git-mount-to-all-of-ccrs-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Warning message broadened from 'git mount' to all of CCR's mounts including gh writes\n\nThe token-mismatch warning now covers git fetches and gh writes, not just git pushes\n\n**What**\n\nThe warning shown when a self-hosted runner session can't re-present its refreshed token was reworded to say that session traffic through Claude Code's mounts, including git pushes and fetches and `gh` (GitHub CLI) writes, may be refused with a `git_token_mismatch` error until a `\/remote` call with that token succeeds.\n\n**Why**\n\nThis makes the warning accurate now that the governed relay covers more than just git pushes, so anyone seeing it understands the fuller range of traffic that could be affected.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}