The session-end hook timeout variable is validated more simply; behaviour is the same.
What's wrong with this entry?
CLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS is now accepted on being greater than zero alone, since the value is already validated as a number earlier. Behaviour is effectively unchanged.
CLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS
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.
-
v2.1.232
Prompt hooks that time out are now logged
Both mention hook timeout
-
v2.1.228
Garbage numeric env vars fall back to defaults
Both mention sessionend hook timeout