Skip to content

1.7.0: mcpp-zed, the backend as a language server of mcpp.toml in Zed, made for Zed's registry - #22

Closed
Sunrisepeak wants to merge 4 commits into
mainfrom
feat/zed-extension
Closed

Sunrisepeak wants to merge 4 commits into
mainfrom
feat/zed-extension

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Closes #21.

What

mide-plugins/zed is mcpp-zed 1.6.0: a Zed extension (mcpp-ide-language-server, listed as mcpp IDE). It starts the backend of series 1.6 as a language server of TOML, which answers completion, hover and diagnostics of mcpp.toml to the editor zed. The backend is unchanged: it already serves an unnamed editor over standard LSP, so no series begins.

  • The backend of its own series. The extension starts the command lsp.mcpp-ide.binary names. Otherwise it downloads mcpp-ide-1.6.0-openkal-bundle-all.tar.gz of v1.6.0 once into its work directory, from GitHub, else from GitCode's xlings-res/mcpp-ide. It starts this system's runner on this architecture's image. It never starts a mcpp-ide from PATH: the extension cannot read the series a backend answers, so it could not refuse a backend of another series.
  • Where it starts. Zed starts it with a worktree's first TOML file. Declining in a worktree without mcpp.toml at its root was measured to show "Failed to run mcpp-ide" in the status bar of every TOML project, and it would also miss projects below the root. The backend reads mcpp.toml and build.mcpp only, so a worktree without one shows nothing.
  • Trust. trusted: true: Zed starts no language server in a worktree it does not trust (measured, below).
  • Zed's registry.
    • The id carries the -language-server suffix the registry asks of an extension that only provides a language server.
    • mide-plugins/zed/LICENSE is Apache-2.0; the registry reads the extension's own directory.
    • The crate is built for wasm32-wasip2 with Rust 1.90, the registry's toolchain.
    • The registry's AI policy admits no agent, so the submission there is a person's. The README states the rules and the four steps.
  • CI.
    • components.tsv gains zed, and test_changes.sh covers it.
    • The zed job runs cargo test, builds for wasm32-wasip2 with ZED_RUST_VERSION (versions.env), and runs .github/scripts/check-zed-extension.sh. That script makes the registry's checks of the manifest and the license, and it fails on a bad id, on a name containing "extension", and on a missing license.
  • Versions. extension.toml is the seventh statement. release-plan.sh reads it, holds Cargo.toml to it (PLUGIN_VERSION is the crate's version), puts zed into vX.Y.0, and accepts zed-vX.Y.Z. release.yml takes zed-v* tags; the release carries no file of its own, because Zed's registry builds the tagged commit.
  • Docs. AGENTS.md (seven statements, the zed tag), README.md and README.zh-CN.md (the Zed column), docs/architecture.md, docs/versions.md, the development skill, CHANGELOG ### zed 1.6.0, and the design record ("Zed, as implemented").

What ran

  • cargo test --locked: 8 passed. They cover the settings over the release, the series' tag and asset, the GitCode URL, each platform's runner and image, the unsupported platforms, the errors and the initialization options.
  • cargo build --locked --release --target wasm32-wasip2 with Rust 1.90: no warning.
  • The registry's own code, run from a checkout of zed-industries/extensions:
    • its license check accepts mide-plugins/zed/LICENSE;
    • validateManifest and validateExtensionsToml pass;
    • its zed-extension CLI, at the SHA its CI pins, packages the directory (provides: ["language-servers"]).
  • release-plan.sh:
    • with no tag: "one series 1.6: … zed 1.6.0";
    • v1.6.0 gives every component, zed included;
    • zed-v1.6.0 gives components=zed;
    • zed-v1.7.1 is refused;
    • a Cargo.toml differing from extension.toml is refused.
  • test_changes.sh, check-sources and check-i18n pass.
  • A real Zed 1.29.3 (xlings' zed), Linux x86_64, under Xvfb with lavapipe. The packaged extension was unpacked under extensions/installed/mcpp-ide-language-server as the registry installs it; PATH was /usr/bin:/bin; Zed's TOML extension was installed by auto_install_extensions.
    • An mcpp project. The extension downloaded mcpp-ide-1.6.0 into its work directory and Zed started the runner on the image, still running 20 s later.
    • The same project with a recording wrapper named in lsp.mcpp-ide.binary with ["serve"]:
      • the client was Zed 1.29.3 with {"editor": "zed", "trusted": true};
      • didOpen of mcpp.toml came with language toml;
      • the server answered mcpp-ide 1.6.0 and published mcpp.manifest.unknownKey ("unknown key colour in [package]").
      • Named without arguments, the wrapper was started with none: Zed itself starts a command named there, so the README says to include serve.
    • A Cargo project. The backend started; there was no error in Zed.log or in the status bar (screenshot), and no diagnostic.
    • An untrusted worktree. Zed.log: "Waiting for worktree … to be trusted, before starting language server mcpp-ide".
  • Not run: macOS and Windows in a real Zed. The runner's and image's names differ there, which cargo test covers.

… Zed, made for Zed's registry

mide-plugins/zed is a Zed extension, mcpp-ide-language-server (mcpp IDE), version 1.6.0: the backend
of its own series as a language server of TOML, which answers completion, hover and diagnostics of
mcpp.toml. It starts the command lsp.mcpp-ide.binary names, else the bundle of v1.6.0, downloaded
once into its work directory from GitHub or the GitCode mirror; not a mcpp-ide from PATH, whose
series it cannot check. It starts with a worktree's first TOML file, since declining elsewhere is
shown as a failure in Zed's status bar and the backend reads only mcpp.toml and build.mcpp.

It meets Zed's registry: the -language-server id, its license in its own directory, Rust 1.90 for
wasm32-wasip2. CI's zed component tests it, builds it so and runs the registry's checks of the
manifest and the license. extension.toml is the series' seventh statement, zed-vX.Y.Z tags a patch,
and its README states the registry's rules and how a person submits it there.

Closes #21.
…ry component

The review of #22 found that the extension sends editor "zed", which protocol.schema.json did not
allow; AGENTS.md §7 asks the schema to change with the behaviour, and the schema is a backend path,
so the Zed extension begins a series. Every component is 1.7.0 and the extension downloads v1.7.0.

Also from the review: Cargo.lock is held to extension.toml by release-plan.sh like Cargo.toml; a
marker written after the bundle is checked says it is whole, so a download cut short is repeated;
the README says that a backend named in the settings is started as it is, and that the GitCode
fallback has a release once its files are mirrored.
@speak-agent speak-agent changed the title feat(zed): mcpp-zed, the backend as a language server of mcpp.toml in Zed, made for Zed's registry 1.7.0: mcpp-zed, the backend as a language server of mcpp.toml in Zed, made for Zed's registry Nov 21, 2026
@speak-agent

Copy link
Copy Markdown
Member

After review

  • Series 1.7.0. The extension sends editor: "zed", which protocol.schema.json did not allow. AGENTS.md §7 asks the schema to change with the behaviour, and protocol/ is a backend path, so this begins series 1.7:
    • the schema names zed in initialize's options and in mcpp-ide/commands/list;
    • all seven statements are 1.7.0, and the extension downloads v1.7.0;
    • CHANGELOG ## 1.7 / ### 1.7.0 replaces the ### zed 1.6.0 entry.
  • The real Zed check needs the release. The extension works in Zed only once v1.7.0 is released, with its bundle, and mirrored to GitCode.
  • release-plan.sh holds Cargo.lock to extension.toml, as it holds Cargo.toml.
  • A completion marker. A marker is written after the bundle is checked, and a directory without it is downloaded again: an unpacking cut short could otherwise leave a runner that exists but is not whole.
  • README. It says that a backend named in lsp.mcpp-ide.binary is started as it is, with no series check, and that the GitCode fallback has a release only once its files are mirrored.
  • Earlier fix. test(vscode): the release's tags include zed-v*, the VS Code gates' failure.

Rerun locally:

  • mcpp build && mcpp test: 14 passed.
  • check-sources and check-i18n pass.
  • VS Code npm test: 550 passed.
  • Neovim smoke over the 1.7.0 backend: 0 failures.
  • Zed cargo test --locked: 8 passed. check-zed-extension.sh passes.
  • release-plan.sh: "one series 1.7 … zed 1.7.0". A Cargo.lock that differs is refused.
  • The marker logic in a real Zed 1.29.3. I ran a copy of the extension set to 1.6.0, the released backend. It downloaded mcpp-ide-1.6.0, wrote its marker (v1.6.0) and kept the backend running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(zed): an extension for Zed, published through Zed's extension registry

2 participants