MCP registry publishing

[nithishr]

• Automated Release Process: A comprehensive release process has been documented in a new RELEASE.md file, detailing steps for version updates, publishing to PyPI, Docker Hub, and the MCP Registry, and handling release candidates.
• Version Management Script: A new helper script, scripts/update_version.sh, has been added to automate the process of updating version numbers across pyproject.toml, server.json, and uv.lock to ensure consistency.
• Version Bump to Release Candidate: The project's version has been updated from 0.5.1 to 0.5.2rc1 across all relevant configuration files (pyproject.toml, server.json, uv.lock), indicating a release candidate for the upcoming version.
• MCP Registry Name in README: The README.md file now includes a comment specifying the MCP registry name for the project.

[gemini-code-assist]

Summary of Changes

Hello @nithishr, I'm Gemini Code Assist¹! 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 significantly enhances the project's release management by introducing a detailed, automated process. It provides clear guidelines for versioning, publishing artifacts to various platforms like PyPI and Docker Hub, and managing release candidates. A new utility script streamlines version updates across the codebase, ensuring consistency and reducing manual errors. The project's version has been incremented to a release candidate to facilitate testing of these new release procedures.

Highlights

• Automated Release Process: A comprehensive release process has been documented in a new RELEASE.md file, detailing steps for version updates, publishing to PyPI, Docker Hub, and the MCP Registry, and handling release candidates.
• Version Management Script: A new helper script, scripts/update_version.sh, has been added to automate the process of updating version numbers across pyproject.toml, server.json, and uv.lock to ensure consistency.
• Version Bump to Release Candidate: The project's version has been updated from 0.5.1 to 0.5.2rc1 across all relevant configuration files (pyproject.toml, server.json, uv.lock), indicating a release candidate for the upcoming version.
• MCP Registry Name in README: The README.md file now includes a comment specifying the MCP registry name for the project.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/update-mcp-registry.yml

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive release process, complete with documentation in RELEASE.md and an automation script, update_version.sh, to streamline version bumping. The documentation is well-written and the script is a great step towards automation. However, I've found a critical issue in the update_version.sh script that would cause version inconsistencies in server.json after the recent changes. I've provided a fix for this. I also have a minor suggestion for the RELEASE.md file to improve clarity. Overall, these are valuable additions for maintaining the project.

[nithishr]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive release process, including detailed documentation in RELEASE.md and a helper script update_version.sh to automate version bumping. The changes are well-thought-out and significantly improve the release workflow. My review includes a couple of suggestions to enhance the clarity of the documentation and add input validation to the new script for increased robustness.