ci(lint): use CI_PYTHON_LAUNCHER from runner config as single source of truth
Configure system Python path once in runner/config.yaml (runner.envs) instead of probing N candidate locations in the workflow. Workflow now fails fast with a clear error if the env is unset or points to a missing file. Document the new env in AGENTS.md.
This commit is contained in:
@@ -38,6 +38,11 @@ runner:
|
||||
# Force UTF-8 stdio for the Python orchestrator (Phase A4) so non-ASCII
|
||||
# characters in build logs survive the act_runner -> Gitea round-trip.
|
||||
PYTHONIOENCODING: "utf-8"
|
||||
# Absolute path to the system Python interpreter used to bootstrap the
|
||||
# production venv (F:\CI\python\venv). act_runner runs as SYSTEM with a
|
||||
# sanitized PATH where neither `python` nor `py.exe` resolve, so workflows
|
||||
# rely on this single source of truth. Update only when upgrading Python.
|
||||
CI_PYTHON_LAUNCHER: "C:\\Program Files\\Python314\\python.exe"
|
||||
|
||||
# Optional: load additional env vars from a file (one KEY=VALUE per line)
|
||||
# env_file: "F:\\CI\\runner.env"
|
||||
|
||||
Reference in New Issue
Block a user