What probably matters to youSection of the release
What
Git can take config settings from environment variables: GIT_CONFIG_COUNT, GIT_CONFIG_KEY_n and GIT_CONFIG_VALUE_n. When you set TLS settings this way, Claude Code now passes them on to the git commands it runs itself, such as a reset --hard. TLS is the encryption used for secure connections. Only http settings like these are passed on:
sslcainfo and sslcapath, the certificate authority bundle
sslverify
sslversion, sslcipherlist and sslbackend
schannelcheckrevoke and schannelusesslcainfo
pinnedpubkey, certificate pinning
proxysslcainfo
Before, those internal git commands ran without these settings.
Why
If you are behind a corporate proxy with a custom certificate bundle set through environment variables, Claude Code's own git operations could fail certificate checks. They now use the same settings as your own git commands.
Read from
Names in the bundleGIT_CONFIG_COUNTGIT_CONFIG_KEY_nGIT_CONFIG_VALUE_n
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 doubtWhich of Claude Code's internal git commands besides the reset receive these settings is not fully known.
Anthropic's release notes agreeFixed worktree checkouts failing certificate verification (for example on Git LFS downloads) when the CA certificate is passed to git as…
