Bump server version to 0.6.0 #172

akolotov · 2025-07-23T00:06:32Z

Summary

bump version to 0.6.0 in pyproject.toml and __init__.py

Testing

ruff check . --fix
ruff format .
ruff check .
ruff format --check .
pytest -q

https://chatgpt.com/codex/tasks/task_b_68802346a7ac83238a79faab39220c5d

Summary by CodeRabbit

Chores
- Updated the application version to 0.6.0.

coderabbitai · 2025-07-23T00:06:38Z

Walkthrough

The version number of the blockscout_mcp_server package was updated from "0.5.0" to "0.6.0" in both the package's __init__.py file and the pyproject.toml configuration file. No other changes were made.

Changes

File(s)	Change Summary
blockscout_mcp_server/init.py	Updated `__version__` from "0.5.0" to "0.6.0".
pyproject.toml	Updated project version from "0.5.0" to "0.6.0".

Estimated code review effort

1 (~2 minutes)

Possibly related PRs

Bump MCP server to v0.5.0 #149: Updates the version string of the package and project version, directly related as a version bump update.
Bump the server version to 0.4.1 #132: Updates the version string in both __init__.py and pyproject.toml, making it directly related.

✨ Finishing Touches

📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (1)

pyproject.toml (1)

3-3: Consider updating ancillary artifacts (CHANGELOG, release notes).

A version bump typically warrants an entry in CHANGELOG.md (or equivalent) and an updated tag/release description so downstream consumers can track what changed.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aee3407 and f6cd70b.

📒 Files selected for processing (2)

blockscout_mcp_server/__init__.py (1 hunks)
pyproject.toml (1 hunks)

📓 Path-based instructions (3)

pyproject.toml

📄 CodeRabbit Inference Engine (.cursor/rules/010-implementation-rules.mdc)

If any new package needs to be installed it needs to be done with 'sudo which uv pip install --system ""' command. Don't forget to update pyproject.toml with the new package.

When updating the version of the MCP server, update the version field in the [project] section of pyproject.toml.

Files:

pyproject.toml

**/*.py

📄 CodeRabbit Inference Engine (.cursor/rules/000-role-and-task.mdc)

**/*.py: The MCP server must be implemented in Python, as you are a senior Python developer and the expertise is in Python.
The MCP server must wrap Blockscout APIs and expose blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol (MCP).
The MCP server must communicate with AI agents/chat applications through stdin.

**/*.py: Regular Python modules should generally not exceed 500 lines of code (LOC). If a module approaches this limit, consider splitting it into multiple focused modules (e.g., address_tools.py and address_tools_advanced.py) to maintain readability and logical organization.
ALL import statements must be placed at the top of the Python module, immediately after the module docstring (if present) and before any other code. Never insert imports inline near where the functionality is used. Follow PEP 8 import order.
ALL linting and formatting issues must be resolved before committing or pushing code. Use the Ruff rules defined in 300-ruff-lint-and-format.mdc to identify and fix issues.

**/*.py: Always run ruff check . --fix and ruff format . on generated code before suggesting commits or opening a PR
Avoid using # noqa: E501 for ordinary code lines; split long lines instead. Only use # noqa: E501 for docstrings or string literals that must exceed 120 characters.
Use Ruff to enforce a 120-character line length, compatible with Black formatting

Files:

blockscout_mcp_server/__init__.py

blockscout_mcp_server/__init__.py

📄 CodeRabbit Inference Engine (.cursor/rules/130-version-management.mdc)

When updating the version of the MCP server, update the __version__ variable in blockscout_mcp_server/__init__.py.

Files:

blockscout_mcp_server/__init__.py

🧠 Learnings (3)

📓 Common learnings

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Applies to blockscout_mcp_server/__init__.py : When updating the version of the MCP server, update the `__version__` variable in `blockscout_mcp_server/__init__.py`.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Update both `pyproject.toml` and `blockscout_mcp_server/__init__.py` simultaneously to maintain consistency across the codebase.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Use the exact same version string in both `pyproject.toml` and `blockscout_mcp_server/__init__.py`.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Applies to pyproject.toml : When updating the version of the MCP server, update the `version` field in the `[project]` section of `pyproject.toml`.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/200-development-testing-workflow.mdc:0-0
Timestamp: 2025-07-22T00:13:24.809Z
Learning: Ensure your changes are well-tested by checking test coverage using pytest --cov=blockscout_mcp_server --cov-report=term-missing

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/000-role-and-task.mdc:0-0
Timestamp: 2025-07-22T00:11:07.532Z
Learning: Applies to **/*.py : The MCP server must wrap Blockscout APIs and expose blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol (MCP).

Learnt from: akolotov
PR: blockscout/mcp-server#142
File: blockscout_mcp_server/api/routes.py:242-258
Timestamp: 2025-07-10T19:21:50.271Z
Learning: The user akolotov prefers a unified tool registration approach where a single function registers tools in both MCP and REST API instead of having separate registration points in blockscout_mcp_server/server.py and blockscout_mcp_server/api/routes.py. This would eliminate duplication and reduce maintenance burden.

Learnt from: akolotov
PR: blockscout/mcp-server#148
File: blockscout_mcp_server/api/routes.py:44-52
Timestamp: 2025-07-11T00:58:37.475Z
Learning: Logging is not currently used in the blockscout/mcp-server codebase. Full logging support will be implemented in a separate issue. Print statements are acceptable temporarily until proper logging is implemented.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-22T00:11:00.226Z
Learning: Read the project technical description in `SPEC.md` to clearly understand how the MCP server communicates with counterparties and important aspects of the server implementation before responding to a user request.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/tools/*.py : Do not expose individual pagination parameters (like page, offset, items_count) in tool signatures; use a single opaque cursor string.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/config.py : For paginated tools, add a dedicated page size configuration variable to blockscout_mcp_server/config.py.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/config.py : Add new API endpoint configuration to blockscout_mcp_server/config.py when introducing a new external API endpoint.

pyproject.toml (13)

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Applies to blockscout_mcp_server/init.py : When updating the version of the MCP server, update the __version__ variable in blockscout_mcp_server/__init__.py.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Update both pyproject.toml and blockscout_mcp_server/__init__.py simultaneously to maintain consistency across the codebase.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Applies to pyproject.toml : When updating the version of the MCP server, update the version field in the [project] section of pyproject.toml.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/130-version-management.mdc:0-0
Timestamp: 2025-07-22T00:12:19.662Z
Learning: Use the exact same version string in both pyproject.toml and blockscout_mcp_server/__init__.py.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/200-development-testing-workflow.mdc:0-0
Timestamp: 2025-07-22T00:13:24.809Z
Learning: Ensure your changes are well-tested by checking test coverage using pytest --cov=blockscout_mcp_server --cov-report=term-missing

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/000-role-and-task.mdc:0-0
Timestamp: 2025-07-22T00:11:07.532Z
Learning: Applies to **/*.py : The MCP server must wrap Blockscout APIs and expose blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol (MCP).

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/tools/*.py : Do not expose individual pagination parameters (like page, offset, items_count) in tool signatures; use a single opaque cursor string.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/config.py : For paginated tools, add a dedicated page size configuration variable to blockscout_mcp_server/config.py.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/config.py : Add new API endpoint configuration to blockscout_mcp_server/config.py when introducing a new external API endpoint.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/tools/*.py : When simplifying address objects in tool outputs, transform complex address objects into a single address string.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/110-new-mcp-tool.mdc:0-0
Timestamp: 2025-07-22T00:12:06.026Z
Learning: Applies to blockscout_mcp_server/server.py : Register each new tool in blockscout_mcp_server/server.py by importing the tool function and registering it with the MCP server using the @mcp.tool() decorator.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/000-role-and-task.mdc:0-0
Timestamp: 2025-07-22T00:11:07.532Z
Learning: Applies to **/*.py : The MCP server must be implemented in Python, as you are a senior Python developer and the expertise is in Python.

Learnt from: CR
PR: blockscout/mcp-server#0
File: .cursor/rules/150-rest-api-implementation.mdc:0-0
Timestamp: 2025-07-22T00:12:50.405Z
Learning: Applies to blockscout_mcp_server/api/routes.py : REST handler functions in api/routes.py MUST be named after the MCP tool they wrap, with an _rest suffix (e.g., get_block_info_rest).

blockscout_mcp_server/__init__.py (13)