[ca] Update GitHub MCP Server to v0.20.0

[github-actions]

Update GitHub MCP Server

Version Update

• Previous: v0.19.1 → New: v0.20.0
• Release Date: 2025-10-27 09:25:40 UTC
• Time Since Last Release: 6 days (v0.19.1 released 2025-10-21)

Breaking Changes

Issues API Consolidation

BREAKING: Multiple issue-related tools have been consolidated into unified tools with method parameters:

Consolidated into issue_read:

• ❌ get_issue → ✅ issue_read with method: "get"
• ❌ get_issue_comments → ✅ issue_read with method: "get_comments"
• ❌ list_labels (with issue_number) → ✅ issue_read with method: "get_labels"
• ❌ list_sub_issues → ✅ issue_read with method: "get_sub_issues"

Consolidated into issue_write:

• ❌ create_issue → ✅ issue_write with method: "create"
• ❌ update_issue → ✅ issue_write with method: "update"

Consolidated into sub_issue_write:

• ❌ add_sub_issue → ✅ sub_issue_write with method: "add"
• ❌ remove_sub_issue → ✅ sub_issue_write with method: "remove"
• ❌ reprioritize_sub_issue → ✅ sub_issue_write with method: "reprioritize"

New Features

Pull Request Improvements

• New get_comments method added to pull_request_read tool
• Provides consistent API with the issues consolidation pattern

Project Enhancements

• fields parameter added to list_project_items tool
• fields parameter added to get_project_item tool
• Enables more granular control over returned project data

Bug Fixes

• Fixed URL parameter descriptions (Fix command trigger conditions to check correct body field per event type #1287)
• Improved OCI package specification in server.json ([WIP] Update workflow to use Codex and adjust Node.js version #1217)
• Updated projects fields and prompts (Add shared markitdown MCP workflow and command-based resource summarizer with persistent storage #1292)

Security

• No CVEs or security patches mentioned in this release

Impact Assessment

Risk Level: High (Breaking Changes)

Affected Features:

• All workflows using GitHub MCP server issue tools
• Workflows using sub-issue management
• Any direct tool references in workflow configurations

Migration Required: Yes

Migration Notes

1. DefaultGitHubToolsLocal and DefaultGitHubToolsRemote in pkg/constants/constants.go:

   • Currently reference old tool names: get_issue, get_issue_comments, list_sub_issues
   • Need to update to new consolidated names: issue_read, issue_write, sub_issue_write

2. Workflow Compatibility:

   • The gh-aw system may need updates to handle the new method-based API
   • Tools that previously worked with direct names may need method parameter support

3. Testing Requirements:

   • Test workflows using issue-related tools
   • Verify sub-issue functionality still works
   • Check project item listing with new fields parameter

CLI Discovery

No CLI changes detected (GitHub MCP Server is a Docker image, not a CLI tool).

Changelog Links

• GitHub Release: https://github.com/github/github-mcp-server/releases/tag/v0.20.0
• Full Changelog: github/github-mcp-server@v0.19.1...v0.20.0
• PR Ensure workspace directory is accessible to copilot engine in threat detection job #1211: Issues consolidation (main breaking change)
• PR Add custom engine support with actions/ai-inference and fix engine config from imported files #1282: Project fields support
• PR Fix command trigger conditions to check correct body field per event type #1287: URL parameter fixes
• PR Add shared markitdown MCP workflow and command-based resource summarizer with persistent storage #1292: Projects fields and prompt updates

Status

✅ Constants updated in pkg/constants/constants.go (v0.19.1 → v0.20.0)
✅ Workflows recompiled successfully with make recompile
⚠️ Action Required: Update default tool lists in constants.go to use new consolidated tool names
⚠️ Testing Required: Verify issue-related workflows still function correctly

---

Checked by: CLI Version Checker workflow
Run ID: 18845612637
Timestamp: 2025-10-27 15:03 UTC

AI generated by CLI Version Checker

[pelikhan]

Review all agentic workflow and update for new tool names