Evidence · DiggingBeagle record
github-mcp-server issue #3751
Original issue and reproduction notes about github mcp issue field edits lost concurrent updates.
- Published
- Nov 9, 2026
- Source role
- primary disclosure
Evidence record
Original issue and reproduction notes about github mcp issue field edits lost concurrent updates.
Claim-level citations (2)
- supportsGitHub MCP issue field edits lost concurrent updates: A repository issue reports: The issue reports 19 lost changes in 30 concurrent pairs, compared with zero in 28 per-field GraphQL controls; pagination may also truncate source state.
Issue #3751, description and reproduction
- supportsGitHub MCP issue field edits lost concurrent updates: The reporter measured 19 lost edits in 30 paired concurrent GitHub MCP issue-field updates, compared with none in 28 direct per-field GraphQL controls.
Issue #3751, paired-write reproduction and comparison against setIssueFieldValue