fix: update invalid docker/setup-qemu-action SHA in release workflow#5704
Conversation
Renamed the second '## Build-tools sysroot image' heading to '## Sysroot staging lifecycle' to resolve MD024/no-duplicate-heading. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
… job The Build Build-Tools Image job pinned docker/setup-qemu-action to SHA a3c050c5b9001e95079e262a6db77c5e7c7c3467 which no longer exists upstream. Update to 49b3bc8e6bdd4a60e6116a5414239cba5943d3cf (v3.2.0), matching the other jobs in this workflow. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
There was a problem hiding this comment.
Pull request overview
This PR fixes a failure in the release workflow by updating a pinned docker/setup-qemu-action commit SHA that no longer resolves. In addition, it refactors config-writer Jest tests to share common mock/lifecycle setup and makes a small documentation heading adjustment for ARC/DinD sysroot staging.
Changes:
- Update
.github/workflows/release.ymlto pindocker/setup-qemu-actionto a valid SHA (49b3bc8e..., v3.2.0) for the Build-Tools image job. - Add a shared config-writer test harness utility and refactor existing config-writer test suites to use it.
- Rename a heading in
docs/arc-dind.mdto better reflect the described sysroot staging behavior.
Show a summary per file
| File | Description |
|---|---|
src/test-helpers/config-writer-test-harness.test-utils.ts |
New shared Jest mock factories + temp-dir lifecycle helpers for config-writer test suites. |
src/config-writer.test.ts |
Refactors config-writer tests to use the shared harness helpers and mock factories. |
src/config-writer-branches.test.ts |
Refactors branch-coverage tests to use the shared harness helpers and mock factories. |
docs/arc-dind.md |
Updates a section heading to better match the sysroot staging content. |
.github/workflows/release.yml |
Fixes failing workflow by updating the pinned docker/setup-qemu-action SHA for the Build-Tools image job. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 5/5 changed files
- Comments generated: 1
- Review effort level: Low
| - name: Set up Docker Buildx | ||
| uses: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f # v3 | ||
|
|
||
| - name: Set up QEMU | ||
| uses: docker/setup-qemu-action@a3c050c5b9001e95079e262a6db77c5e7c7c3467 # v3 | ||
| uses: docker/setup-qemu-action@49b3bc8e6bdd4a60e6116a5414239cba5943d3cf # v3.2.0 |
|
⏳ Copilot review left inline comments. @lpcox To proceed:
|
|
@copilot address review feedback |
…e-writeconfigs-setup
|
✅ Smoke Copilot BYOK AOAI (Entra) completed. Copilot AOAI BYOK (Entra) mode operational. 🔓 |
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤 |
|
📡 Smoke OTel Tracing completed. All tracing scenarios validated. ✅ |
|
✅ Smoke Claude passed |
|
✅ Contribution Check completed successfully! Contribution check complete for PR #5704: the change is limited to updating a pinned GitHub Action SHA in the release workflow; the PR description is clear, no new functionality requires tests or docs, and file placement is appropriate. |
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟 |
|
✅ Build Test Suite completed successfully! |
|
🔌 Smoke Services — All services reachable! ✅ |
|
✅ Smoke Gemini completed. All facets verified. 💎 |
|
Chroot tests passed! Smoke Chroot - All security and functionality tests succeeded. |
|
🔑 Smoke Copilot PAT PAT auth validated. All systems operational. ✅ |
|
🚀 Security Guard has started processing this pull request |
|
✅ Smoke Copilot BYOK completed. Copilot BYOK mode operational. 🔓 |
|
✅ Smoke Copilot BYOK AOAI (api-key) completed. Copilot AOAI BYOK (api-key) mode operational. 🔓 |
Smoke Test: Claude Engine Validation
Overall result: PASS ✅
|
🔍 Smoke Test ResultsPR: fix: update invalid docker/setup-qemu-action SHA in release workflow
Overall: FAIL — Pre-step data (
|
Smoke Test: Copilot BYOK (Direct) Mode ✅All Tests Passed
Status: PASS – Running in direct BYOK mode with COPILOT_PROVIDER_API_KEY forwarding through api-proxy sidecar.
|
|
@lpcox
|
Smoke Test: Copilot PAT Auth — ✅ PASS
Auth mode: PAT (COPILOT_GITHUB_TOKEN) • @lpcox (author)
|
🔍 Smoke Test: API Proxy OpenTelemetry Tracing
All scenarios pass. OTEL tracing integration is fully functional.
|
|
5702: refactor: extract shared config-writer test harness to eliminate duplicate setup Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "registry.npmjs.org"See Network Configuration for more information.
|
Gemini Engine Smoke Test Results
Overall status: PASS Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "localhost"See Network Configuration for more information.
|
🧪 Chroot Version Comparison Results
Overall: ❌ FAILED — Python and Node.js versions differ between host and chroot environments.
|
|
@lpcox Running in direct BYOK mode (COPILOT_PROVIDER_API_KEY + COPILOT_PROVIDER_BASE_URL) via api-proxy → Azure OpenAI (Foundry, o4-mini-aw) Overall: PASS
|
Smoke Test: Services Connectivity
Overall: FAIL
|
🏗️ Build Test Suite Results
Overall: 8/8 ecosystems passed — ✅ PASS
|
Add docs/model-api-mapping.json mapping OpenAI and Anthropic models to their supported API endpoints (chat/completions vs responses vs messages). Add an agentic workflow that refreshes the mapping daily from official provider documentation and opens a PR if changes are detected. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Problem
The "Build Build-Tools Image" job in the release workflow fails at "Set up job" with:
Failed run: https://github.com/github/gh-aw-firewall/actions/runs/28415298993/job/84196839108
Fix
Update the pinned SHA to
49b3bc8e6bdd4a60e6116a5414239cba5943d3cf(v3.2.0), which is the same valid SHA already used by the other image build jobs in this workflow.