Repository navigation
Pin the MCP server the plugin delivers, and join the consumer register - #18
Merged
Merged
Conversation
.mcp.json ran `uvx idfkit-mcp` with no version, so every editor got whatever was newest on the day and a release reached users the moment it published, reviewed by nobody (feature 004 of the unification, FR-015). It now pins idfkit-mcp@0.9.3, the newest release. The user still types no version. .lsp.json is unchanged: idfkit-lsp has never been published to PyPI, so there is no version to pin and the entry resolves nothing today (#17). The consumer register records that as a not-yet lag rather than pinning something that does not exist. CODEOWNERS puts both files under review (FR-016), and the README and AGENTS.md no longer teach the unpinned form.
The consumer-register job calls check-consumer.yml at governance-2026.18, which is not cut yet, so it fails until it is. bump-idfkit.yml is dispatched in wave 2: it refuses an idfkit level until idfkit-mcp has a release pinning it, naming idfkit-mcp (FR-020), then moves .mcp.json to that release. The language server cannot move while idfkit-lsp is unpublished, and the pull request says so rather than pretending. decline_reason records a deliberate lag (FR-024). rehearse-candidate.yml rehearses through the two servers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of feature 004 of the unification.
Waits on
governance-2026.18, cut from idfkit/idfkit-conformance#10. The newconsumer-registerjob and the rehearsal pin that tag, so they stay red until it exists. Merge after the tag is cut..mcp.jsonpinsidfkit-mcp@0.9.3. Two installs separated by a release now run the same server. The user still types no version (/plugin install idfkit@idfkit, FR-019). README and AGENTS.md taught the unpinned form and are corrected..lsp.jsonis unchanged, because there is nothing to pin. idfkit-lsp has never been published to PyPI (The language server path resolves nothing: idfkit-lsp is not on PyPI #17), so that entry resolves nothing on a clean machine. The register records it as anot-yetlag..mcp.jsonand.lsp.json(FR-016).bump-idfkit.ymladopts after its servers publish on the level. The MCP half proceeds when idfkit-mcp has. The LSP half stays unchanged, and the PR says so, until idfkit-lsp publishes.consumer-registerjob intests.yml, plusrehearse-candidate.yml(through its providers).All 25 discovery tests pass.