-
Notifications
You must be signed in to change notification settings - Fork 169
fix: Adapt to GitHub MCP Tooling Consolidation #354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Adapt to GitHub MCP Tooling Consolidation #354
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
94d9cce to
9cc452a
Compare
|
LGTM |
The current Docker image reference for GitHub MCP is using 'latest'. This is error-prone and has led to recent failures due to breaking changes, such as tool name consolidations introduced in [v0.18.0](https://github.com/github/github-mcp-server/releases/tag/v0.18.0) where the `get_pull_request*` tools used in this repo were renamed and consolidated.
The underlying GitHub MCP server tooling for pull request read operations has been consolidated, moving away from individual tools like `get_pull_request*` into a single tool `pull_request_read` with multiple methods. Changes were made on [v0.18.0](https://github.com/github/github-mcp-server/releases/tag/v0.18.0) of the GitHub MCP server.
The underlying GitHub MCP server tooling for pull request read operations has been consolidated, moving away from individual tools like `get_pull_request*` into a single tool `pull_request_read` with multiple methods. Changes were made on [v0.18.0](https://github.com/github/github-mcp-server/releases/tag/v0.18.0) of the GitHub MCP server.
9cc452a to
4841daa
Compare
jerop
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @cperez08!
## What's Changed * Move `gemini-invoke` to custom command. by @joshualitt in #348 * Move rest of prompts to custom commands. by @joshualitt in #350 * Normalize tool names in prompts. by @joshualitt in #351 * Fix interpolation syntax. by @joshualitt in #357 * Switch to local telemetry and upload manually to GCP by @joshualitt in #361 * fix: Adapt to GitHub MCP Tooling Consolidation by @cperez08 in #354 * refactor(ci): prioritize event triggers in dispatch workflow by @jerop in #366 * fix(action): correct upload artifacts condition by @jerop in #368 ## New Contributors * @joshualitt made their first contribution in #348 * @cperez08 made their first contribution in #354 **Full Changelog**: v0.1.13...v0.1.14
This pull request addresses recent workflow failures where the Gemini CLI could not perform review tasks due to breaking changes in the GitHub MCP server.
These changes were introduced in the GitHub MCP server's latest release, which consolidated the
get_pull_request*tools into a singlepull_request_readwith multiple methods.Key Changes and Fixes
latest. This prevents unexpected disruptions from future upstream updates and ensures consistent action stability.reviewandinvokeworkflows and examples.For full details on the upstream changes, see the GitHub MCP Server release notes:
v0.18.0 Release Notes
Fixes #353