Runner hook errors saying hooks need Linux or macOS exist but can never trigger.
The Windows guard's platform argument defaults to linux and no caller overrides it, so it never throws.
What's wrong with this entry?
New errors were added saying that lifecycle hooks and orchestrator mode need a Linux or macOS host, because hooks are POSIX executables spawned directly. In this build the check cannot trigger: both call sites pass only the feature name, and the platform argument defaults to linux, so the guard always returns without throwing.
- One message reads
--hooks-dir is not supported on Windows. - Whether it ever fires depends on a caller passing a real platform value, which nothing in this build does.
--hooks-dir is not supported on Windows
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