Repository navigation
Pin the language server the plugin delivers: idfkit-lsp 0.2.0 - #19
Merged
Merged
Conversation
idfkit-lsp reached PyPI for the first time today, so the entry that resolved nothing on a clean machine (#17) now names a version, and two installs separated by a release run the same server (FR-015). --prerelease=allow is needed while idfkit-lsp depends on idfkit 1.0.0rc1: uv takes a pre-release of an indirect dependency only when told to. It sits after the pin so the level stays at args[1], where the consumer register reads it. Verified: this exact command imports the server at 0.2.0 and serves stdio.
… is pinned The previous commit spread the args array over seven lines where this file, like .mcp.json, keeps it on one; only the pin and the flag change. AGENTS.md still said the entry was unpinned until idfkit-lsp published, which it now has.
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
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.
Closes #17.
idfkit-lsp was published to PyPI for the first time today (v0.2.0), so
.lsp.jsoncan finally name a version. Until now it ranuvx --from idfkit-lsp, which resolved nothing on a clean machine.Why
--prerelease=allow: idfkit-lsp 0.2.0 depends onidfkit==1.0.0rc1, and uv installs a pre-release of an indirect dependency only when told to. Without the flag it stops with "pre-releases weren't enabled". The flag can go once idfkit-lsp depends on a stable idfkit. It sits after the pin, so the level stays atargs[1], where the consumer register reads it.Verified: this exact command installs idfkit-lsp 0.2.0 with idfkit 1.0.0rc1, imports the server, and serves stdio. The discovery tests pass.
Merge before idfkit/idfkit-conformance's paired PR, which closes this consumer's lag and marks the
.lsp.jsondeclaration exact. With the register ahead of the plugin, the plugin's self-check would fail at the next governance tag.