fix: recompile lock files with gh-aw v0.68.3#941
Merged
Conversation
Lock files were compiled with v0.66.1 but PRs #919/#920 bumped gh-aw to 0.68.1 without recompiling. The version mismatch caused all agent workflows to fail with: ! 2 MCP servers were blocked by policy: 'github', 'safeoutputs' Recompiled all 8 workflows with gh-aw v0.68.3 (latest). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Recompiles agentic workflow lock files to align runtime Actions configuration with the repo’s updated gh-aw tooling, resolving the previously broken agent workflows caused by a compiler/setup version mismatch.
Changes:
- Regenerates workflow
.lock.ymlfiles withgh-awv0.68.3 metadata and updated pinned action SHAs/containers. - Updates embedded workflow behavior to match newer
gh-awtemplates (e.g.,actions/github-script@v9withgetOctokit, Copilot CLI pinned to1.0.21, AWFv0.25.20, MCPGv0.2.19). - Refreshes
.github/aw/actions-lock.jsonentries for the updated setup/github-script versions.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/test-analysis.lock.yml | Recompiled lock workflow for Test Suite Analysis to gh-aw v0.68.3 with updated pinned actions/containers and newer runtime steps. |
| .github/workflows/perf-analysis.lock.yml | Recompiled lock workflow for Performance Analysis to gh-aw v0.68.3 with updated pinned actions/containers and newer runtime steps. |
| .github/workflows/feature-planner.lock.yml | Recompiled lock workflow for Feature Planner to gh-aw v0.68.3 with updated pinned actions/containers and newer runtime steps. |
| .github/workflows/code-health.lock.yml | Recompiled lock workflow for Code Health Analysis to gh-aw v0.68.3 with updated pinned actions/containers and newer runtime steps. |
| .github/aw/actions-lock.json | Updates locked SHAs for actions/github-script@v9 and github/gh-aw-actions/setup@v0.68.3. |
This was referenced Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Recompiles all 8 agent workflow lock files with gh-aw v0.68.3. The lock files were still compiled with v0.66.1 after PRs #919/#920 bumped gh-aw to 0.68.1 without recompiling, creating a version mismatch that caused all agent workflows to fail.
Root Cause
The stale v0.66.1 setup actions configured the sandbox with outdated firewall and MCP gateway versions. As the platform evolved, this mismatch caused the sandbox policy layer to block both MCP servers:
Without MCP access, agents cannot call
noop,create_pull_request, or any safe-output tool — every run fails.What Changed
gh-aw-actions/setupactions/github-script"latest""1.0.21"No
.mdworkflow files were changed — only.lock.ymlfiles andactions-lock.json.Affected Issues
Closes #940