Repository navigation
Deliver idfkit-lsp 0.3.0 (idfkit 1.1.1) - #27
Merged
Merged
Conversation
samuelduchesne
added a commit
that referenced
this pull request
Oct 19, 2026
idfkit-lsp is published to PyPI since 0.2.0, and the header comment that said otherwise was stale (idfkit-plugin#17 is closed). The bump moved only .mcp.json, so the EnergyPlus delivery-pins step, which checks both pins, waited until .lsp.json was moved by hand (#27 during the 26.2.0 adoption). The run now looks up the newest idfkit-lsp release on the level and moves .lsp.json in the same pull request. When idfkit-lsp has none yet, the MCP half proceeds alone, as before, and the pull request says so.
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.
Summary
Moves the language-server pin in
.lsp.jsonfromidfkit-lsp==0.2.0toidfkit-lsp==0.3.0.idfkit==1.0.0rc1, which does not bundle the EnergyPlus 26.2.0 schema. idfkit-lsp 0.3.0 resolvesidfkit==1.1.1, which does..mcp.jsonand.lsp.json. The.mcp.jsonpin already passes (idfkit-mcp@0.11.1). This change is the remaining half; the adoption runs 39302497910 and 39304017108 both stopped atwaiting on: delivery-pins.bump-idfkit.ymlmoves only.mcp.json, so this pin is changed by hand.Tracking: idfkit/idfkit-conformance#27.
After merge
Re-dispatch
adopt-energyplus.ymlwithrelease=26.2.0. It should then pass the delivery pins and propose the skill-text rewrite.