[Release-0.5.1] Update version to 0.5.1 in pyproject.toml, server.json, and uv.lock

[nithishr]

No description provided.

[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 focuses on a routine version bump, incrementing the project's version from 0.5.0 to 0.5.1. This update is crucial for maintaining accurate release tracking and ensuring that all associated package metadata and deployment configurations reflect the current state of the project, preparing it for a new release cycle.

Highlights

• Version Update: The project version has been updated from 0.5.0 to 0.5.1 across multiple configuration files.
• Configuration Files Modified: Changes were applied to pyproject.toml, server.json, and uv.lock to reflect the new version.
• Docker Image Identifier: The Docker image identifier in server.json was updated to docker.io/couchbaseecosystem/mcp-server-couchbase:0.5.1.

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 updates the project version from 0.5.0 to 0.5.1 across pyproject.toml, server.json, and uv.lock. The changes are consistent and correctly reflect the new version for this release. My review includes one suggestion to improve the maintainability of the release process by automating the version updates from a single source of truth, which would reduce the risk of manual errors in the future.

[gemini-code-assist]

The version number is hardcoded in multiple places in this file (lines 9, 14, 175) and also in pyproject.toml. Manually updating the version in multiple locations is error-prone and can lead to inconsistencies during releases.

To improve maintainability, consider using a single source of truth for the version number, for example, in pyproject.toml. A release script could then read this version and automatically update all other files, including server.json.

For example, you could use a tool like jq in a script to update this file:

# Assuming VERSION is set, e.g., VERSION="0.5.1"
jq --arg v "$VERSION" \
  '.version = $v | .packages[0].version = $v | .packages[1].identifier = "docker.io/couchbaseecosystem/mcp-server-couchbase:" + $v' \
  server.json > server.json.tmp && mv server.json.tmp server.json

This would make the release process more robust and less dependent on manual search-and-replace.