Skip to content

Add AWF installer failure and platform regression coverage - #76193

Draft
gh-aw-bot with Copilot wants to merge 2 commits into
mainfrom
copilot/harden-awf-binary-installation-step
Draft

gh-aw-bot with Copilot wants to merge 2 commits into
mainfrom
copilot/harden-awf-binary-installation-step

Conversation

Copilot AI commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

AWF startup failures need actionable download diagnostics, and Windows-generated install steps must use the supported Bash shell. The installer already retries downloads and verifies checksums; this change adds regression coverage for those behaviors and platform-specific lock generation.

  • Download diagnostics: Simulate a failed curl request and verify its underlying error is preserved in the installer output.
  • Platform lock files: Verify generated Linux and Windows locks retain the checksum pin, and Windows selects Bash while Linux keeps its default shell.
- name: Install AWF binary
  shell: bash # Windows runner
  run: bash "${RUNNER_TEMP}/gh-aw/actions/install_awf_binary.sh" v0.28.62 --checksums-sha256 <digest>

Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot AI changed the title [WIP] Harden AWF binary installation startup step Add AWF installer failure and platform regression coverage Nov 9, 2026
Copilot AI requested a review from gh-aw-bot November 9, 2026 09:02

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[AW Top 10] 05 Harden AWF binary installation startup step

2 participants