The self-hosted runner writes server-supplied hook scripts for a session and deletes them afterwards.
What's wrong with this entry?
When the server supplies hook scripts with a session, the runner validates and writes them under hooks/.ccr-launcher alongside a launcher-settings.json, then deletes them when the session ends. Scripts must have known event names, match ^[a-zA-Z0-9][a-zA-Z0-9_-]{0,62}\.(py|sh)$, and stay under a per-script size cap. A hooks path that is not a directory is refused.
- outcomes report through a new
self_hosted_launcher_hookstelemetry family, including a distinct case where a repo settings file setsdisableAllHooks:true - runner path only; nothing happens unless the server sends the hooks with the session
self_hosted_launcher_hooks_validation_failed
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.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner