This PR drops the `Architecture::x86` variant within the extension API. Reason for this being that - Zed itself is not shipped for 32 bit and thus this variant is never actually constructed - we don't support a Node runtime in 32 bit environments - basically all language and context servers do not ship 32 bit variants Thus, this PR removes support for this variant, as currently, extension authors always have to return an error for the missing 32 bit support of their binaries. With this, this will no longer be needed. Lastly, this removes one space of too much indentation I found whilst doing these changes. Very visible in the GitHub UI luckily. Release Notes: - Removed support for extensions downloading language servers, debuggers and MCP servers on 32-bit architecture. Extensions may still work if you manually specify a path to an appropriate binary, but will not succeed when attempting to download a binary based on the current systems 32-bit architecture.
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.