Skip to content

v0.5.0

Choose a tag to compare

@samuelduchesne samuelduchesne released this 13 Nov 15:20
2c91991

This release makes the VS Code extension work as packaged. The VSIX now carries the language service it needs, the release workflow publishes it to the Visual Studio Marketplace, and the extension no longer starts the source server on an interpreter that cannot run it. The minimum versions rise to VS Code 1.90 and Node 20. Neither server gains or loses a capability.

Raised minimum versions

  1. VS Code 1.90 (previously 1.86) (#38). VS Code 1.90 is the first release on Electron 29, whose Node 20 runtime is the one the model server runs on by default. VS Code 1.86 to 1.89 run Node 18, which the @idfkit packages the model server depends on do not support.
  2. Node 20 (previously 18) for the npm package @idfkit/language-server (#38). This matches engines.node in @idfkit/core, @idfkit/idfkit and @idfkit/language 0.4.0. The bundle now targets node20.

Users of VS Code 1.86 to 1.89, and editors that run idfkit-language-server on Node 18, should remain on 0.4.0 until they upgrade. The Python source server is not affected.

Features

  • Visual Studio Marketplace publishing (#41): the release workflow packages the extension, checks the VSIX, attaches it to the GitHub release, and publishes that same file to the Marketplace through Trusted Publishing, with no stored token. Prereleases are skipped, because the Marketplace accepts only major.minor.patch.
  • python -m idfkit_lsp --version (#43): prints the source server's level and exits. It answers only after the server and its libraries have loaded, so its exit status states whether an interpreter can run the server.
  • Comment toggling for .idf files in VS Code (#40): a language-configuration.json holds the line comment marker and nothing else. It is recorded in capabilities.json as an editor-specific limitation, because the protocol has no request through which a server could supply it. Other editors configure their own marker.
  • Package headers (#48, #49): the README, the npm package and the PyPI package open with the idfkit identity header. The PyPI package gains a description, which it previously lacked.

Fixes

  • The packaged extension now carries the language service (#37). A VSIX built with vsce package contained no @idfkit package, so the model server could not resolve @idfkit/idfkit and advertised no model text capability. The npm package @idfkit/language-server was not affected.
  • The source server is not started on an interpreter that cannot run it (#43). The extension first asks the configured interpreter for -m idfkit_lsp --version. On failure, the reason goes to the output channel and one information message appears per interpreter. This replaces the error notification, the five restarts and the unhandled rejections that every Python file previously caused on a machine without the server.
  • A source server that closes during startup is no longer restarted.
  • idfkit: Restart Language Servers reads idfkitLsp.pythonPath again, so a corrected setting takes effect without reloading the window. idfkit: Open Documentation states why it cannot answer when the source server is not running.
  • Clearing idfkitLsp.pythonPath now means python3, as documented, rather than an empty command.

Other changes

  • The source server depends on idfkit 1.2.0 (previously 1.1.1) (#31).
  • The Marketplace listing is written for users; development material moved to CONTRIBUTING.md (#36).
  • .vscodeignore is an allowlist. Agent instructions, the Python server's source, tool configuration, levels.json and source maps no longer ship in the VSIX (#39).
  • CI builds the VSIX from a clean checkout, checks that its model server advertises what capabilities.json marks present, and runs the protocol suite against it (#42).

Upgrade notes

  • VS Code users on 1.90 or newer: upgrade transparently. Install from the Marketplace once the listing is live, or from the VSIX attached to this release.
  • Python source server: uv tool install -U idfkit-lsp or pip install -U idfkit-lsp. No configuration change is required. It now resolves idfkit 1.2.0.
  • Other editors using the model server: npm install -g @idfkit/language-server@latest on Node 20 or newer.