You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[awf-feature-surfacing] Align runner.installation schema and generated reference with rootless installer behavior #75999
runner.installation was added in commit 5147c4e to select CLI installation privilege independently of runner topology. Its schema description and generated frontmatter reference now disagree with the current Linux installer behavior and the dedicated runner guidance.
Key issue
The schema says rootless installation uses ~/.local/bin and defaults to privileged installation outside ARC/DinD. Current Linux installers use the job-scoped $RUNNER_TEMP/gh-aw/bin directory, and when no installation mode is specified they fall back to rootless if neither root nor passwordless sudo is available. The generated full frontmatter reference repeats the stale schema text. This can lead authors and editor users to expect the wrong install path or sudo requirement.
Evidence
pkg/parser/schemas/main_workflow_schema.json (runner.installation, near line 3329): describes ~/.local/bin and a privileged default outside ARC/DinD.
docs/src/content/docs/reference/frontmatter-full.md (near line 2549): repeats that description.
actions/setup/sh/install_privileges.sh: selects $RUNNER_TEMP/gh-aw/bin for Linux rootless installation and falls back when passwordless sudo is unavailable.
actions/setup/sh/install_copilot_cli.sh and actions/setup/sh/install_threat_detect_binary.sh: call the shared privilege and path setup.
.github/aw/syntax-core.md (runner.installation) and docs/src/content/docs/reference/self-hosted-runners.md describe the current path and fallback.
Next actions
P1: Update the runner.installation schema description to state the Linux job-scoped path and the actual no-sudo fallback. Clarify how an explicit privileged setting behaves when sudo is unavailable.
P1: Regenerate the full frontmatter reference and editor metadata derived from the schema so both surfaces agree with the installer and runner guidance.
P2: Add a focused consistency check for the schema description and generated reference to catch stale path and default claims.
Activity
lpcox commentedon Nov 9, 2026
🔗 AWF tracking issue: #aw_track2