The runner can pass a settings file to sessions; its Windows hooks guard never actually fires.
A guard rejecting hooks dirs and orchestrator mode on Windows exists but its platform argument defaults to "linux", so it never triggers.
What's wrong with this entry?
The self-hosted runner launcher now takes a path to a settings file and passes it to the session it spawns as --settings, and settings is added to the argument names the server is not allowed to override. A separate guard is meant to fail with an explanation when --hooks-dir, SELF_HOSTED_RUNNER_HOOKS_DIR or orchestrator mode is used on Windows, but its platform argument defaults to the literal "linux" and both callers rely on that default, so it never fires in this build.
- The reserved-argument list stops a server-provided config from replacing your settings path.
- The Windows error text explains that orchestrator mode depends on the spawn-runner lifecycle hook.
orchestrator mode is not supported on Windows: it is driven by the spawn-runner lifecycle hook
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