chore: v0.1.6 — MCP Registry hotfix release

[ayhammouda]

Summary

Patch release on top of v0.1.5 to unblock MCP Registry publication.

v0.1.5 published successfully to PyPI with attestations, but the publish-mcp-registry job in release run #25876196215 failed at the Validate server.json step:

expected length <= 100   location: body.description   (value was 152 chars)

apps#30 shortened server.json description to 96 chars on main and pre-validated it with the actual mcp-publisher binary against the live registry endpoint:

$ ./mcp-publisher validate server.json
Validating against https://registry.modelcontextprotocol.io...
✅ server.json is valid

v0.1.6 ships the corrected server.json so MCP Registry catches up. Same wheel content as v0.1.5; the only functional difference is the registry metadata.

Changes

• Bump 0.1.5 → 0.1.6 in the three lockstep files:
  • pyproject.toml:7
  • server.json:11 (top-level)
  • server.json:17 (packages[0].version)
  • uv.lock (regenerated)
• CHANGELOG.md v0.1.6 entry under ### Fixed

Verified locally

• ✅ uv build produces python_docs_mcp_server-0.1.6-py3-none-any.whl + .tar.gz
• ✅ Clean-venv install: python-docs-mcp-server --version reports 0.1.6
• ✅ mcp-publisher validate server.json against the real registry endpoint: VALID
• ✅ All three locked anchor phrases (canonical Python stdlib oracle / always free, always MIT / token-frugal) preserved in the 96-char description

What lands after merge + tag

Tagging v0.1.6 triggers .github/workflows/release.yml:

1. build — verifies version triple lockstep, runs lint/type/test, builds wheel + sdist
2. publish — PyPI publish (Trusted Publishing + Sigstore)
3. publish-mcp-registry — this time validation passes; MCP Registry receives v0.1.6 metadata
4. github-release — creates GH Release v0.1.6 with the dist artifacts attached

Test plan

• mcp-publisher validate against live registry endpoint → ✅
• uv build + clean-venv install + version check
• CI green on PR
• After merge + tag: all 4 release.yml jobs green
• After release: uvx --refresh python-docs-mcp-server --version returns 0.1.6 from a clean shell
• MCP Registry shows v0.1.6

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes

  • Corrected the server description field in configuration metadata to comply with registry validation schema requirements and character length constraints.

• Documentation

  • Updated the changelog to document the version 0.1.6 release, detailing configuration corrections and the preservation of documentation elements.

• Chores

  • Released version 0.1.6 with updated version numbers across project configuration files, server manifest, and package metadata.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4fd7569d-4c9c-4d89-9b99-7b3904a2c9f9

📥 Commits

Reviewing files that changed from the base of the PR and between 1a74ad7 and a3b5d3f.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• CHANGELOG.md
• pyproject.toml
• server.json

---

📝 Walkthrough

Walkthrough

This PR bumps the project version from 0.1.5 to 0.1.6 across configuration files and adds a changelog entry. The version update is coordinated in pyproject.toml, server.json, and CHANGELOG.md, with the changelog entry documenting a fix to server.json's description length to satisfy MCP Registry's schema constraint.

Changes

Version 0.1.6 Release

Layer / File(s)	Summary
Version bump across configuration and changelog pyproject.toml, server.json, CHANGELOG.md	Version incremented from 0.1.5 to 0.1.6 in pyproject.toml and both the top-level and package entry in server.json. A new 0.1.6 changelog entry documents the fix to server.json's description field to comply with MCP Registry's ≤100 character schema limit.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A version bump hops through the files,
From five to six, with registry smiles,
Description trimmed to fit the frame,
The changelog sings the release's name!

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/pypi-v016

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}