Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Git config location variables are now treated as file paths

Claude Code now treats GIT_CONFIG_GLOBAL and GIT_CONFIG_SYSTEM as environment variables that point to a single file

Under the hood Internal Changes
JSON All of v2.1.282
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.282,
Internal ChangesSection of the release

Unclear What Claude Code does differently with variables sorted as file paths is not known.

What

Claude Code sorts some environment variables (named values your system passes to programs) by whether they point to a file or a folder. GIT_CONFIG_GLOBAL and GIT_CONFIG_SYSTEM, which tell Git where its configuration files are, are now sorted as file paths, alongside variables such as JAVACMD and CLOUDSDK_PYTHON.

Why

These two variables are now handled the same way as other variables that point to a single file.

Read from
Names in the bundleGIT_CONFIG_GLOBAL
What the documentation says
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat Claude Code does differently with variables sorted as file paths is not known.

See this entry in the whole of v2.1.282 →

Feedback