zed/extensions
Piotr Osiewicz c9534e8025
chore: Use workspace fields for edition and publish (#23291)
This prepares us for an upcoming bump to Rust 2024 edition.

Release Notes:

- N/A
2025-01-17 17:39:22 +01:00
..
csharp chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
deno chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
elixir chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
emmet chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
erlang chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
glsl chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
haskell chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
html chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
lua chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
perplexity chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
php chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
prisma chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
proto chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
purescript chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
ruff chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
scheme Add inclusive range scope overrides. Don't auto-close quotes at the ends of line comments (#20206) 2024-11-04 15:36:39 -08:00
slash-commands-example chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
snippets chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
terraform chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
test-extension chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
toml chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
uiua chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
zig chore: Use workspace fields for edition and publish (#23291) 2025-01-17 17:39:22 +01:00
.gitignore Provide wasm extensions with APIs needed for using pre-installed LSP binaries (#9085) 2024-03-08 17:18:06 -05:00
EXTRACTION.md Document extension extraction process (#19085) 2024-10-11 16:33:40 -04:00
README.md Document extension bump process (#18872) 2024-10-08 16:13:56 -04:00

Zed Extensions

This directory contains extensions for Zed that are largely maintained by the Zed team. They currently live in the Zed repository for ease of maintenance.

If you are looking for the Zed extension registry, see the zed-industries/extensions repo.

Structure

Currently, Zed includes support for a number of languages without requiring installing an extension. Those languages can be found under crates/languages/src.

Support for all other languages is done via extensions. This directory (extensions/) contains a number of officially maintained extensions. These extensions use the same zed_extension_api available to all Zed Extensions for providing language servers, tree-sitter grammars and tree-sitter queries.

Dev Extensions

See the docs for Developing an Extension Locally for how to work with one of these extensions.

Updating

Note

This update process is usually handled by Zed staff. Community contributors should just submit a PR (step 1) and we'll take it from there.

The process for updating an extension in this directory has three parts.

  1. Create a PR with your changes. (Merge it)

  2. Bump the extension version in:

    • extensions/{language_name}/extension.toml
    • extensions/{language_name}/Cargo.toml
    • Cargo.lock

    You can do this manually, or with a script:

    # Output the current version for a given language
    ./script/language-extension-version <langname>
    
    # Update the version in `extension.toml` and `Cargo.toml` and trigger a `cargo check`
    ./script/language-extension-version <langname> <new_version>
    

    Commit your changes to a branch, push a PR and merge it.

  3. Open a PR to zed-industries/extensions repo that updates the extension in question

Edit extensions.toml in the extensions repo to reflect the new version you set above and update the submodule latest Zed commit.

# Go into your clone of the extensions repo
cd ../extensions

# Update
git checkout main
git pull
just init-submodule extensions/zed

# Update the Zed submodule
cd extensions/zed
git checkout main
git pull
cd -
git add extensions.toml extensions/zed