Skip to content

Conversation

@allenhutchison
Copy link
Contributor

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @allenhutchison, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on maintaining up-to-date dependencies and refining error handling within the application. It ensures compatibility with the latest version of a core SDK and improves the robustness of data validation by correctly processing Zod validation errors.

Highlights

  • Dependency Update: The @modelcontextprotocol/sdk dependency has been bumped from ^1.22.0 to ^1.23.0 in both package.json and package-lock.json.
  • Zod Dependency Update: The zod package has been updated to 4.1.13 and zod-to-json-schema to 3.25.0 in package-lock.json. Additionally, the zod peer dependency range for @modelcontextprotocol/sdk has been adjusted to ^3.25 || ^4.0.
  • ZodError Handling Fix: Error handling for ZodError instances in workspace-server/src/utils/validation.ts has been updated to correctly access validation messages using error.issues[0].message instead of error.errors[0].message.
  • Package-lock.json Cleanup: Several peer: true properties have been removed from various dependency entries within package-lock.json, likely reflecting changes in how these dependencies are managed or declared.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly bumps the @modelcontextprotocol/sdk dependency and addresses a breaking change in zod by updating ZodError handling from error.errors to error.issues. The changes are necessary and well-implemented. I have left one suggestion to refactor duplicated validation logic to improve long-term maintainability.

@allenhutchison allenhutchison merged commit 76fcafa into main Dec 2, 2025
6 checks passed
@allenhutchison allenhutchison deleted the adh/feature/bump-mcp-dependency branch December 2, 2025 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants