Bump version to 0.4.0

[fatherlinux]

Summary

• Bump version to 0.4.0 across pyproject.toml, init.py, and server.py
• MINOR bump for new trove_quality tool added in feat: per-file error tracking with trove_quality tool #2

Test plan

• Merge, tag v0.4.0, confirm GHA rebuild triggers

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello, 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 synchronizes the project's version number across all relevant configuration and source files to 0.4.0. This update reflects recent feature additions, specifically the trove_quality tool, ensuring consistency in version reporting throughout the application.

Highlights

• Version Bump: The project version has been updated from 0.3.0 to 0.4.0 across pyproject.toml, __init__.py, and server.py. This is a MINOR bump, reflecting the addition of the trove_quality tool in a previous pull request (feat: per-file error tracking with trove_quality tool #2).

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.

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 PR correctly bumps the version to 0.4.0 in pyproject.toml, __init__.py, and server.py. However, this manual process across multiple files is error-prone. I've left a suggestion to consolidate the version number to a single source of truth to simplify future version bumps. Additionally, I noticed the version number is also hardcoded in Containerfile (line 30) and is currently out of date (0.2.0). While this file isn't part of the current changes, it would be beneficial to update it as well to ensure consistency across the project.

[gemini-code-assist]

To avoid manually updating the version in multiple files, consider making pyproject.toml the single source of truth. You can then read the version dynamically in your code using importlib.metadata. This prevents inconsistencies and simplifies future version bumps.

For example:

In src/mcp_trove_crunchtools/__init__.py:

from importlib import metadata

try:
    __version__ = metadata.version("mcp-trove-crunchtools")
except metadata.PackageNotFoundError:
    # package is not installed, e.g., in development
    __version__ = "0.0.0-dev"

Then, in src/mcp_trove_crunchtools/server.py, you can simply import it:

from . import __version__

mcp = FastMCP(
    "mcp-trove-crunchtools",
    version=__version__,
    # ...
)

This change would make version management more robust.