Version numbers in multiple places

[nithishr]

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.

Originally posted by @gemini-code-assist[bot] in #70 (comment)

[nithishr]

It has been fixed now in #75 by creating a script to update the versions uniformly. And the process has been documented