{"version":"2.1.280","anchor":"git-checkpoint-env-now-derives-from-a-pinned-release-with-g","canonical_anchor":"git-checkpoint-env-now-derives-from-a-pinned-release-with-g","heading":"Git checkpoint env now derives from a pinned release, with graft-file fallback preserved","tier":"internal","area":"Git Checkpoints","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-checkpoint-env-now-derives-from-a-pinned-release-with-g","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git checkpoint env now derives from a pinned release, with graft-file fallback preserved\n\nGit checkpoint environment variables now come from a pinned release, falling back to \/dev\/null only when needed\n\n**What**\n\nWhen Claude Code builds the environment variables used for git checkpoints, it now reads them from a pinned release's own environment first. The `GIT_GRAFT_FILE` variable (a git setting used to graft commit history) is only set to `\/dev\/null` if that pinned environment doesn't already provide a value. Previously, `\/dev\/null` was always used unconditionally.\n\n**Why**\n\nThis lets the pinned release's own git configuration take precedence for checkpoint operations, while still falling back to the old safe default when nothing else specifies one.\n\n- Area: Git Checkpoints\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}