Publish latest VSIX from CI

Author: CryZe

.github/workflows/check.yml

@@ -72,3 +72,54 @@ jobs:
 
       - name: Run the repository verification matrix
         run: cargo xtask check
+
+  vscode-release:
+    name: Publish latest VS Code extension
+    needs: repository
+    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+
+    steps:
+      - name: Check out the repository
+        uses: actions/checkout@v7
+
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: wasm32-unknown-unknown
+
+      - name: Install Node.js
+        uses: actions/setup-node@v7
+        with:
+          node-version: 24
+          cache: npm
+          cache-dependency-path: editors/vscode/package-lock.json
+
+      - name: Install extension dependencies
+        working-directory: editors/vscode
+        run: npm ci
+
+      - name: Package the extension
+        working-directory: editors/vscode
+        run: npm run package:vsix -- --out splitscript-latest.vsix
+
+      - name: Publish the latest release
+        shell: bash
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          asset="editors/vscode/splitscript-latest.vsix"
+          title="Latest SplitScript VS Code Extension"
+          notes="Continuously updated from the latest verified commit on master. This early build may introduce breaking language changes."
+
+          git tag --force latest "$GITHUB_SHA"
+          git push --force origin refs/tags/latest
+
+          if gh release view latest >/dev/null 2>&1; then
+            gh release edit latest --title "$title" --notes "$notes" --latest
+            gh release upload latest "$asset" --clobber
+          else
+            gh release create latest "$asset" --verify-tag --title "$title" --notes "$notes" --latest
+          fi

README.md

@@ -40,10 +40,12 @@ documentation catalog, formatter, diagnostics, and language service.
 
 ### Visual Studio Code authors
 
-Install a supplied `splitscript-*.vsix`, open a saved `.split` file, and run
-**SplitScript: Open Documentation**. The bundled **Getting started** guide is a
-self-contained, compiler-checked path through attachment, settings, state
-snapshots, builds, diagnostics, and host loading.
+Install the [latest SplitScript VSIX][latest-vsix], open a saved `.split` file,
+and run **SplitScript: Open Documentation**. The bundled **Getting started**
+guide is a self-contained, compiler-checked path through attachment, settings,
+state snapshots, builds, diagnostics, and host loading. The package is rebuilt
+from every verified push to `master`, so it is an early moving build rather than
+a stable release.
 
 Use **SplitScript: Start Debug Watch** while editing and **SplitScript: Build
 Release** for the final module. Both write a neighboring `.wasm` file. The
@@ -131,3 +133,5 @@ instantiate it.
 The repository also contains ports and deterministic runtime fixtures used as
 implementation evidence. They are not the user guide, are not compatibility
 promises, and should not be treated as templates for new scripts.
+
+[latest-vsix]: https://github.com/CryZe/SplitScript/releases/download/latest/splitscript-latest.vsix

TODO.md

@@ -837,6 +837,10 @@ debug watch without external executables. Native `splitc` and `splitls` remain
 separate first-class products. The architecture experiment is complete; the
 remaining work is product hardening and distribution.
 
+- [x] Publish a platform-neutral VSIX from every verified `master` push. CI
+  moves the stable `latest` tag and replaces `splitscript-latest.vsix` on one
+  durable GitHub release; pull requests and other branches remain read-only.
+
 - [x] Add cooperative cancellation points to expensive compiler stages so a
   superseded editor build can stop work rather than merely have its completed
   response discarded. The shared compiler and service distinguish typed

editors/vscode/DEVELOPMENT.md

@@ -34,6 +34,12 @@ npm run package:vsix
 The production build runs automatically and writes
 `splitscript-<version>.vsix` in this directory.
 
+After the complete verification job succeeds for a push to `master`, CI runs
+the same production packaging path with the stable asset name
+`splitscript-latest.vsix`. It moves the `latest` tag to that verified commit and
+replaces the asset on the existing **Latest SplitScript VS Code Extension**
+release. Pull requests and pushes to other branches never publish a package.
+
 ## Worker architecture
 
 The language client gives the language server its own worker and Wasm instance.

editors/vscode/README.md

@@ -7,8 +7,9 @@ separate native executable.
 
 ## Start a script
 
-1. Install the supplied `splitscript-*.vsix` with **Extensions: Install from
-   VSIX**.
+1. Download the [latest SplitScript VSIX][latest-vsix] and install it with
+   **Extensions: Install from VSIX**. This early package follows every verified
+   push to `master` and may contain breaking language changes.
 2. Open a folder and create a saved file ending in `.split`.
 3. Run **SplitScript: Open Documentation** and open **Getting started**. That
    compiler-checked guide introduces process attachment, a typed setting, one
@@ -83,3 +84,5 @@ reported without losing the failing state.
 If a build targets the wrong file, make sure the intended `.split` editor is
 active when starting the command. Untitled files prompt for a save location;
 the resulting saved document is the one compiled.
+
+[latest-vsix]: https://github.com/CryZe/SplitScript/releases/download/latest/splitscript-latest.vsix