chore(vscode): release 0.51.0 tracking leo-lsp 4.4.1

Author: mohammadfawaz

CONTRIBUTING.md

@@ -20,10 +20,13 @@ npm run package:vscode
 
 ## Local Leo LSP Testing
 
-For local language-server validation, install `leo-lsp` so the executable is
-available on `PATH`, or point the extension at it explicitly with the
-`leo.languageServer.path` setting.
+For local language-server validation, install the supported `leo-lsp` version:
 
-When the extension finds `leo-lsp`, it starts the Rust language server over
-stdio. When it does not find the binary, the extension stays in its
-tree-sitter-derived fallback mode instead of failing activation.
+```bash
+cargo install leo-lsp --version 4.4.1 --locked
+leo-lsp --version
+```
+
+The executable must be available on `PATH`. You can also set `leo.languageServer.path` to its absolute path.
+
+When the extension finds `leo-lsp`, it starts the Rust language server over stdio. When it does not find the binary, the extension uses its tree-sitter-derived fallback mode.

package-lock.json

@@ -1,12 +1,11 @@
 # Leo VS Code Extension
 
-This package contains the Leo 4.0 VS Code extension scaffold for the existing
-`aleohq.leo-extension` marketplace entry.
+This package contains the Leo VS Code extension for the existing `aleohq.leo-extension` Marketplace entry.
 
 ## Current Scope
 
 - Leo language registration for `.leo` files
-- Leo 4.0-aware TextMate fallback highlighting
+- TextMate fallback highlighting generated from the released Leo grammar
 - Optional `leo-lsp` startup when a local server binary is available
 - LSP-backed go-to-definition when `leo-lsp` advertises definition support
 - Approximate workspace-wide go-to-definition fallback when `leo-lsp` is unavailable
@@ -21,26 +20,20 @@ validation notes.
 
 ## Syncing Tree-Sitter Source
 
-For current testing before a Leo 4.0 release tag exists, fetch the latest Leo
-`master` in the sibling checkout and then run:
+To test an unreleased grammar, fetch the latest Leo `master` branch in the sibling checkout and run:
 
 ```bash
 git -C ../leo fetch origin master
 npm run sync:tree-sitter
 ```
 
-For the actual Leo 4.0 release process, sync from the Leo 4.0 release tag
-instead of from `master` so the extension ships against the released language
-syntax:
+For a release, sync from the corresponding `leo-lang` tag so that the extension uses the released language syntax:
 
 ```bash
-./scripts/sync-tree-sitter-from-leo.sh ../leo <leo-4.0-tag>
+./scripts/sync-grammar-artifacts.sh ../leo leo-lang-v4.4.1
 ```
 
-The plan is to test from `master` for now, then publish the updated
-`aleohq.leo-extension` marketplace package after Leo mainnet ships. Because the
-extension identity stays the same, existing VS Code users should receive the
-update automatically.
+The extension identity does not change, so existing VS Code users receive Marketplace updates automatically.
 
 ## Generated Syntax Artifacts
 
@@ -112,13 +105,12 @@ npm run package:vscode
 
 ## Manual Marketplace Publish
 
-Once `VSCODE_PUBLISHER_TOKEN` is configured for this repository, maintainers can
-publish from the Actions tab with `.github/workflows/publish-vscode-extension.yml`.
+Once `VSCODE_PUBLISHER_TOKEN` is configured for this repository, maintainers can publish from the Actions tab with `.github/workflows/publish-vscode-extension.yml`.
 
 The manual workflow:
 
 - checks out the default branch
-- requires an exact version input such as `0.49.1`
+- requires an exact version input such as `0.51.0`
 - builds the extension and uploads `dist/leo-extension.vsix`
 - publishes `aleohq.leo-extension` to the VS Code Marketplace
 - leaves the repository version untouched, so a follow-up commit can sync repo

packages/vscode/Developer.md

@@ -51,6 +51,19 @@ Today it supports:
 - optional `leo-lsp` startup for semantic tokens and go-to-definition when the binary is installed locally
 - approximate client-side go-to-definition fallback when `leo-lsp` is unavailable
 
+### Install the language server
+
+This extension is tested with [`leo-lsp` 4.4.1](https://github.com/ProvableHQ/leo/releases/tag/leo-lsp-v4.4.1).
+
+Install the supported version from crates.io:
+
+```bash
+cargo install leo-lsp --version 4.4.1 --locked
+leo-lsp --version
+```
+
+The extension finds `leo-lsp` in the Cargo binary directory, on `PATH`, or at the path in the `leo.languageServer.path` setting. The extension continues with fallback definitions if the binary is not available.
+
 ### 🛠️ Migration Status
 
 The previous LSP-backed implementation is being replaced as part of the migration to faster Rust-based Leo tooling.

packages/vscode/README.md

@@ -1,9 +1,9 @@
 {
   "name": "leo-extension",
   "displayName": "Leo",
-  "version": "0.50.0",
+  "version": "0.51.0",
   "publisher": "aleohq",
-  "description": "The official VS Code extension for Leo",
+  "description": "The official VS Code extension for Leo, tested with leo-lsp 4.4.1",
   "license": "SEE LICENSE IN LICENSE.txt",
   "engines": {
     "vscode": "^1.82.0"
@@ -58,7 +58,7 @@
         "leo.languageServer.path": {
           "type": "string",
           "default": "",
-          "markdownDescription": "Absolute or workspace-relative path to the `leo-lsp` executable. When unset, the extension searches common local development locations and `PATH`."
+          "markdownDescription": "Absolute or workspace-relative path to the `leo-lsp` executable. This release is tested with `leo-lsp` 4.4.1. When unset, the extension searches common local development locations and `PATH`."
         },
         "leo.languageServer.args": {
           "type": "array",

packages/vscode/package.json

@@ -1,7 +1,11 @@
 import * as vscode from "vscode";
 
 import { createLeoDefinitionProvider } from "./definitionProvider";
-import { activateLeoLanguageServer, deactivateLeoLanguageServer } from "./languageServer";
+import {
+  activateLeoLanguageServer,
+  deactivateLeoLanguageServer,
+  SUPPORTED_LEO_LSP_VERSION
+} from "./languageServer";
 
 export function activate(context: vscode.ExtensionContext): void {
   const selector = [{ language: "leo", scheme: "file" }];
@@ -16,7 +20,7 @@ export function activate(context: vscode.ExtensionContext): void {
   context.subscriptions.push(
     vscode.commands.registerCommand("leo-extension.about", async () => {
       await vscode.window.showInformationMessage(
-        "Leo 4.0 support includes tree-sitter-derived syntax tooling, optional leo-lsp startup, LSP-backed go-to-definition when leo-lsp is available, and approximate fallback definitions when it is not."
+        `Leo includes tree-sitter-derived syntax tooling, optional leo-lsp startup, LSP-backed go-to-definition, and approximate fallback definitions. This extension is tested with leo-lsp ${SUPPORTED_LEO_LSP_VERSION}.`
       );
     })
   );

packages/vscode/src/extension.ts

@@ -9,6 +9,8 @@ const SERVER_COMMAND = "leo-lsp";
 const LANGUAGE_SERVER_PATH_SETTING = "languageServer.path";
 const LANGUAGE_SERVER_ARGS_SETTING = "languageServer.args";
 
+export const SUPPORTED_LEO_LSP_VERSION = "4.4.1";
+
 let client: LanguageClient | undefined;
 
 /**
@@ -39,7 +41,19 @@ export function activateLeoLanguageServer(
   client = languageClient;
   void languageClient.start().then(
     () => {
-      outputChannel.appendLine("leo-lsp started.");
+      const serverVersion = languageClient.initializeResult?.serverInfo?.version;
+      if (serverVersion === SUPPORTED_LEO_LSP_VERSION) {
+        outputChannel.appendLine(`leo-lsp ${serverVersion} started.`);
+      } else if (serverVersion) {
+        const compatibilityMessage =
+          `leo-lsp ${serverVersion} started. This extension is tested with leo-lsp ${SUPPORTED_LEO_LSP_VERSION}.`;
+        outputChannel.appendLine(compatibilityMessage);
+        void vscode.window.showWarningMessage(compatibilityMessage);
+      } else {
+        outputChannel.appendLine(
+          `leo-lsp started without reporting a version. This extension is tested with leo-lsp ${SUPPORTED_LEO_LSP_VERSION}.`
+        );
+      }
     },
     error => {
       outputChannel.appendLine(`Failed to start leo-lsp: ${describeError(error)}`);