Skip to content

Upgrade pinned github-mcp-server from v0.32.0 to v0.33.0+ to fix thread resolution #21130

@microsasa

Description

@microsasa

Request

Upgrade the pinned ghcr.io/github/github-mcp-server Docker image from v0.32.0 to the next release that includes PR github/github-mcp-server#1919.

Why

The resolve_pull_request_review_thread safe-output is unusable with v0.32.0. Agents cannot discover PRRT_ thread node IDs through the available MCP tools, so they hallucinate IDs that fail at the GraphQL API.

github/github-mcp-server#1919 (merged 2026-03-13, closes #1768) added resolve_thread and unresolve_thread methods to pull_request_review_write, and get_review_comments already returns thread IDs in the ID field. This gives agents a path to discover real thread IDs and resolve threads through the MCP tool directly.

v0.32.0 was released 2026-03-06 — one week before the fix merged.

Evidence

gh-aw's own smoke tests consistently skip thread resolution because agents can't obtain thread IDs:

When agents attempt to resolve threads instead of skipping, they fabricate IDs:

Agent provided:  PRRT_kwDOOIiPrc6djnf7 (wrong — doesn't match repo node ID space)
Actual thread:   PRRT_kwDORibwsM50cYP7 (correct)

##[error]Failed to resolve review thread: Could not resolve to a node
  with the global id of 'PRRT_kwDOOIiPrc6djnf7'

Impact

Any workflow using resolve-pull-request-review-thread safe-output is broken. Pipelines with required_conversation_resolution enabled on branch protection cannot auto-merge PRs that receive inline review comments — threads are addressed (replies posted, code fixed) but never resolved.

Environment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions