{"version":"2.1.268","anchor":"new-undigested-cache-staleness-state-in-git-attributeshoo","canonical_anchor":"new-undigested-cache-staleness-state-in-git-attributeshoo","heading":"New 'undigested' cache-staleness state in git-attributes\/hook expansion resolver","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-undigested-cache-staleness-state-in-git-attributeshoo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New 'undigested' cache-staleness state in git-attributes\/hook expansion resolver\n\nGit hook\/attribute file expansion gains a new 'undigested' state for stale cached files\n\n**Unclear.** The finding does not say what user-visible effect the `undigested` state has, only that the resolver can now return it.\n\n**What**\n\nThe internal logic that expands file references in git hook and attribute configuration now tracks a modification 'stamp' for each file path, and can report a new `undigested` result when a file's cached state hasn't caught up with its current content. This sits alongside the existing not_text, unbounded, unexpandable, and contributes result kinds.\n\n**Why**\n\nThis distinguishes files that simply haven't been processed yet from other reasons expansion might fail, which should make caching in this area more accurate.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}