Release Notes: v1.1.1 – Features, Bug Fixes, Documentation, and Maintenance

[LadyKerr]

Release Notes

✨ Features

• Default Toolset Configuration
  You can now use a special default toolset keyword to quickly enable the standard toolset configuration (context, repos, issues, pull_requests, users). This makes CLI toolset configuration easier and tidier, cleaning up invalid entries and surfacing clear warnings for unrecognized toolsets. CLI help text is updated for clarity.
  #1229

• GitHub Support Docs Search Tool
  New tool github_support_docs_search added for retrieving GitHub product and support documentation directly via the MCP Server.
  #1225

• Ignore Unknown Toolsets Option
  Unknown toolsets can now be optionally ignored instead of causing errors—making configuration more forgiving.
  #1202

• Consolidated Pull Request Review Tools
  The following tools have been unified under a single pull_request_review_write with method parameters (create, submit_pending, delete_pending):

  • create_and_submit_pull_request_review
  • create_pending_pull_request_review
  • submit_pending_pull_request_review
  • delete_pending_pull_request_review
    This streamlines pull request review actions and makes the API more predictable.
    #1192

---

🐛 Bug Fixes

• Subdomain Isolation URL Parsing for GHES
  Improved detection/support for subdomain isolation in GitHub Enterprise Server (GHES). Better feedback in the get_file_contents tool improves context for LLM integrations.
  #1218

---

📝 Documentation

• Remote-Only Toolsets Clarified
  The README now clearly highlights remote-only toolsets and documentation, making configuration easier for remote users.
  #1227
• Gemini CLI Documentation Link
  The documentation now points to the MCP Configuration Structure for extra Gemini CLI configuration options, and duplicates are removed from code examples.
  #1223
• GHES/GHEC Documentation Visibility
  Refactored documentation to better highlight GHES and GHEC configuration, fixing example URLs and addressing frequent questions.
  #1210

---

🔧 Internal/Maintenance

• Registry Release Pipeline Simplified
  The registry release workflow is more reliable and secure:
  • Waits for Docker image availability before proceeding
  • Uses version tag triggers (no elevated permissions needed)
  • Includes a fail-safe 5-minute timeout
    #1204

---

Changes included since previous release: v0.18.0 (2025-10-10)