randomparity / randomparity/kdive
MCP spec drift: upstream 2026-07-28 not yet adopted
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 26m
- Merged PRs (30d)
- 311
Description
The MCP specification repository publishes revision `2026-07-28`, which is
newer than the revision KDIVE declares (`2025-11-25`, in
`src/kdive/mcp/__init__.py`).
Every unadopted revision, oldest first: `2026-07-28`.
This is a report, not a regression: KDIVE negotiates whatever the pinned
`mcp` dependency supports, so adopting a newer revision needs an `mcp`
release that supports it first. See ADR-0537.
When that lands: edit `src/kdive/mcp/__init__.py`, then run
`just doc-constants` and `just resources-docs` and commit the
regenerated files. `just mcp-spec-check` verifies the result.
Filed by `.github/workflows/mcp-spec-drift.yml`. It will not file again
for `2026-07-28` while an issue naming it exists, open or closed.
Contributor guide
Research direction
Wait for an mcp release supporting revision 2026-07-28, then update the revision in src/kdive/mcp/__init__.py. Run just doc-constants and just resources-docs, commit the regenerated files, and use just mcp-spec-check to verify that the declared revision and generated documentation are correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100