agentic-workflow updates (network, integrity, upd of gh aw)#65926
agentic-workflow updates (network, integrity, upd of gh aw)#65926DeagleGross wants to merge 12 commits intodotnet:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the repository’s gh-aw–generated agentic workflows to the newer gh-aw toolchain and refreshes the compiled/locked workflow outputs, including network and integrity guard configuration changes used by the GitHub MCP server integration.
Changes:
- Recompiled gh-aw locked workflows to gh-aw v0.62.5 and updated referenced action SHAs/binary versions (e.g., AWF v0.24.5, MCPG v0.1.20).
- Moved gh-aw runtime assets from
/opt/gh-aw/...to${{ runner.temp }}/${RUNNER_TEMP}paths and adjusted Safe Outputs paths accordingly. - Updated the issue triage workflow definition to allow additional network domains and set GitHub tool integrity filtering to
none.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
.github/workflows/test-quarantine.lock.yml |
Recompiled locked workflow to gh-aw v0.62.5; updates runtime paths, firewall/container versions, and conclusion gating. |
.github/workflows/issue-triage-agent.md |
Updates workflow frontmatter to configure github.min-integrity: none and expand allowed network domains. |
.github/workflows/issue-triage-agent.lock.yml |
Recompiled locked workflow to gh-aw v0.62.5; updates runtime paths, firewall/container versions, MCP guard policy config, and conclusion gating. |
.github/aw/actions-lock.json |
Consolidates pinned gh-aw setup action version to v0.62.5. |
| "GITHUB_HOST": "\${GITHUB_SERVER_URL}", | ||
| "GITHUB_PERSONAL_ACCESS_TOKEN": "\${GITHUB_MCP_SERVER_TOKEN}", | ||
| "GITHUB_READ_ONLY": "1", | ||
| "GITHUB_TOOLSETS": "context,repos,issues,pull_requests" | ||
| }, |
There was a problem hiding this comment.
The GITHUB_TOOLSETS value here does not include search, but the triage agent workflow relies on searching for duplicate issues (e.g., search_issues). Without enabling the search toolset, the GitHub MCP server may not expose the search tools and duplicate detection will fail.
Consider adding search back to GITHUB_TOOLSETS (or otherwise ensuring the search_issues capability is enabled for this MCP server instance).
|
Marked as draft for now: latest |
|
It got unblocked |
Several things done here:
gh awand recompiled merged workflows to 0.62.5min-integrity: noneas per docs. Problem I am solving is that seems like there is another update fromgh awwhich dissalows MCP calls for searching issues: