A bad CLAUDE_CODE_GIT_BASH_PATH on Windows now warns and auto-detects instead of quitting.
What's wrong with this entry?
On Windows, pointing the variable at a path that does not exist used to print an error and call process.exit(1). It now warns and carries on.
- Falls back to normal auto-detection instead of exiting
- The path is additionally rejected unless its basename is bash.exe, sh.exe, bash or sh
- Windows git-bash lookup only
falling back to auto-detection
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.