{"version":"2.1.229","anchor":"self-hosted-runner-requires-base-dir-on-windows-and-validate","canonical_anchor":"self-hosted-runner-requires-base-dir-on-windows-and-validate","heading":"Self-hosted runner requires --base-dir on Windows and validates launcher hooks","tier":"use","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/self-hosted-runner-requires-base-dir-on-windows-and-validate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Self-hosted runner requires `--base-dir` on Windows and validates launcher hooks\n\nOn Windows the self-hosted runner now requires --base-dir, and launcher hook config is validated.\n\n**What**\n\nOn Windows the self-hosted runner has no default working directory, so `--base-dir` (or the `SELF_HOSTED_RUNNER_BASE_DIR` environment variable) must now be supplied; the help text says so. A new `launcher_hooks` config section is also checked at load: every entry must name a known hook event and point at a `.py` or `.sh` filename matching a restricted pattern, and duplicate entries are rejected regardless of letter case.\n\n**Details**\n\n- Config now records whether the base directory came from the built-in default or from `SELF_HOSTED_RUNNER_BASE_DIR`.\n- Other platforms keep their existing default base directory.\n\n**Evidence**\n\n`required on Windows, which has no default`\n\n- Area: Self-Hosted Runner\n- Names: `--base-dir`, `SELF_HOSTED_RUNNER_BASE_DIR`, `launcher_hooks`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}