Release on GitHub release

RELEASE.md

@@ -2,14 +2,12 @@
 
 ## Bumping Dependencies
 
-1. Change dependency
-2. Upgrade lock with `uv lock --resolution lowest-direct
+1. Change dependency version in `pyproject.toml`
+2. Upgrade lock with `uv lock --resolution lowest-direct`
 
 ## Major or Minor Release
 
-1. Create a release branch named `vX.Y.Z` where `X.Y.Z` is the version.
-2. Bump version number on release branch.
-3. Create an annotated, signed tag: `git tag -s -a vX.Y.Z`
-4. Create a github release using `gh release create` and publish it.
-5. Have the release flow being reviewed.
-7. Bump version number on `main` to the next version followed by `.dev`, e.g. `v0.4.0.dev`.
+Create a GitHub release via UI with the tag being `vX.Y.Z` where `X.Y.Z` is the version,
+and the release title being the same. Then ask someone to review the release.
+
+The package version will be set automatically from the tag.

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mcp"
-version = "1.4.0.dev0"
+dynamic = ["version"]
 description = "Model Context Protocol SDK"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -52,9 +52,17 @@ dev-dependencies = [
 ]
 
 [build-system]
-requires = ["hatchling"]
+requires = ["hatchling", "uv-dynamic-versioning"]
 build-backend = "hatchling.build"
 
+[tool.hatch.version]
+source = "uv-dynamic-versioning"
+
+[tool.uv-dynamic-versioning]
+vcs = "git"
+style = "pep440"
+bump = true
+
 [project.urls]
 Homepage = "https://modelcontextprotocol.io"
 Repository = "https://github.com/modelcontextprotocol/python-sdk"