Bump version to 0.3.1

Patch release shipping the Context-schema fix that landed in #7. With
the bug in 0.3.0, every MCP client call returned `ctx Field required`
because `from __future__ import annotations` hid the Context parameter
from FastMCP's detection, so the server is effectively unusable on 0.3.0
and 0.3.1 is the first working release.

Author: cobanov

CHANGELOG.md

@@ -4,6 +4,14 @@ All notable changes to this project are documented in this file. The format foll
 
 ## [Unreleased]
 
+## [0.3.1] - 2026-05-21
+
+### Fixed
+- FastMCP exposed the internal `Context` parameter (`ctx`) as a required client-facing tool argument on every tool, so MCP clients failed every call with `ctx Field required`. `from __future__ import annotations` made FastMCP see the annotation as a string and miss the Context-detection branch; the fix patches `__annotations__["ctx"]` back to the real `Context` class before registering each tool. ([#7](https://github.com/cobanov/teslamate-mcp/pull/7))
+
+### Added
+- Regression test that constructs the server and asserts `ctx` is absent from every tool's MCP-facing `inputSchema` while `run_sql` still requires `query`.
+
 ## [0.3.0] - 2026-05-21
 
 ### Added

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teslamate-mcp"
-version = "0.3.0"
+version = "0.3.1"
 description = "A Model Context Protocol (MCP) server that exposes your TeslaMate database to AI assistants over stdio and streamable HTTP."
 readme = "README.md"
 license = { text = "MIT" }