Address review: one publish step, no mkdocs watch list, stable classifier

- publish-pypi: build both packages into one dist/ and publish in a single
  step with skip-existing, so a partially failed upload is fixed by
  re-running the job rather than by step ordering.
- mkdocs: drop the watch package list instead of extending it.
- The Development Status classifier is permanently 5 - Production/Stable;
  say so in RELEASE.md and set it on mcp-types, which #2975 left at Alpha.

Author: maxisbey

.github/workflows/publish-pypi.yml

@@ -28,8 +28,8 @@ jobs:
 
       - name: Build
         run: |
-          uv build --package mcp-types -o dist/types
-          uv build --package mcp -o dist/mcp
+          uv build --package mcp
+          uv build --package mcp-types
 
       - name: Upload artifacts
         uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
@@ -56,18 +56,9 @@ jobs:
           name: release-dists
           path: dist/
 
-      # The `mcp` wheel exact-pins `mcp-types`, so the dependency must publish
-      # first: if its upload fails, nothing `mcp`-named has been uploaded yet and
-      # `pip install mcp` keeps resolving to the previous release. `skip-existing`
-      # lets a re-run after a failed `mcp` upload get past the already-published
-      # `mcp-types`; the `mcp` step omits it so a duplicate upload still fails loudly.
-      - name: Publish mcp-types to PyPI
+      - name: Publish package distributions to PyPI
         uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # release/v1
         with:
-          packages-dir: dist/types
+          # Lets a re-run after a partially failed upload publish the remaining
+          # files instead of erroring on the ones already on PyPI.
           skip-existing: true
-
-      - name: Publish mcp to PyPI
-        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # release/v1
-        with:
-          packages-dir: dist/mcp

RELEASE.md

@@ -28,8 +28,10 @@ version, and the `mcp` wheel exact-pins `mcp-types`. Before the first release
 that includes both, the `mcp-types` PyPI project must be given the same
 trusted publisher as `mcp` (this repository, workflow `publish-pypi.yml`,
 environment `release`) and the same owners — without it the `mcp-types`
-upload is rejected. The publish workflow uploads `mcp-types` first so that a
-failed upload stops the job before anything `mcp`-named has been published.
+upload is rejected. If only some of the files upload, fix the cause and re-run
+the publish job — `skip-existing` makes it skip whatever already landed. The
+`Development Status` classifier in both `pyproject.toml` files is permanently
+`5 - Production/Stable`; it is not bumped as part of any release.
 
 1. Check the full test matrix is green on the release commit. The matrix runs
    with `continue-on-error`, so a green workflow run does not mean the tests

mkdocs.yml

@@ -101,10 +101,6 @@ markdown_extensions:
       custom_checkbox: true
   - sane_lists # this means you can start a list from any number
 
-watch:
-  - src/mcp
-  - src/mcp-types
-
 plugins:
   - search
   - social:

src/mcp-types/pyproject.toml

@@ -14,7 +14,7 @@ maintainers = [
 keywords = ["mcp", "llm", "automation"]
 license = { text = "MIT" }
 classifiers = [
-    "Development Status :: 3 - Alpha",
+    "Development Status :: 5 - Production/Stable",
     "Intended Audience :: Developers",
     "License :: OSI Approved :: MIT License",
     "Programming Language :: Python :: 3",