SessionEnd hooks no longer see a bypass_permissions_disabled reason, since nothing can end your session that way.
What's wrong with this entry?
The reason a SessionEnd hook receives is now one of five values: clear, resume, logout, prompt_input_exit and other. The bypass_permissions_disabled value is gone from the whole build, along with the mid-session check that used to log a warning and exit with it, so nothing emits it any more.
- The hook schema and the runtime list now agree, and the hook documentation's matcher values are generated from the same shared constant instead of being hardcoded a second time.
prompt_input_exit, "clear", "resume", "logout", "prompt_input_exit", "other"
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.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook
-
v2.1.236
Some hook events take a separate dispatch path
Both mention hook