{"version":"2.1.280","anchor":"git-store-staleness-check-now-also-compares-objects-stamp","canonical_anchor":"git-store-staleness-check-now-also-compares-objects-stamp","heading":"Git store-staleness check now also compares objects stamp","tier":"internal","area":"Git Integration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-store-staleness-check-now-also-compares-objects-stamp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git store-staleness check now also compares objects stamp\n\nGit store freshness checks now also compare an objects timestamp, not just info\/pack\/alternates\n\n**What**\n\nThe check Claude Code uses to decide whether a cached git store is still fresh now also compares the `objects` timestamp between the current state and the stored stamps, in addition to the existing `info`, `pack`, `alternates`, and `httpAlternates` comparisons it already made.\n\n**Why**\n\nThis makes the staleness check more thorough, catching cases where the underlying git objects changed even if the other tracked components didn't, so a stale cache is less likely to be used.\n\n- Area: Git Integration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}