mirror of
https://github.com/zed-industries/zed.git
synced 2026-08-24 08:24:58 +00:00
original uri https://github.com/zed-industries/zed
https://zed.dev
09e809bd83
context_server's Cargo.toml requested http_client's test-support
feature from its normal [dependencies], not just for its own tests.
Because Cargo unifies features per package across a build, this
activated http_client/test-support for every build that links
context_server at all, including a plain release build of the zed
binary itself: cargo tree -p zed -e normal,features showed the
feature resolved with no dev-dependency involved.
The only user of that feature in context_server was
http_client::FakeHttpClient, used exclusively inside #[cfg(test)]
modules in oauth.rs and transport/http.rs. Moving the feature request
to [dev-dependencies] (matching the existing gpui/test-support entry)
keeps those tests building while dropping test-support from every
non-test build, including benchmarks' resolved feature graph, which
previously had a single test-support occurrence traced to exactly
this edge.
Also extended script/check-gpui-bench-feature-isolation with a check
that scans benchmarks' entire resolved feature graph for the literal
test-support feature name, so any future direct or transitive
dependency reintroducing it fails loudly. While adding that check,
found and fixed a latent bug affecting every existing check in the
script: echo "${output}" | grep --quiet PATTERN races under
set -o pipefail, since grep --quiet exits after its first match
without draining stdin, which can SIGPIPE echo before it finishes
writing large output and turn a real match into a false negative (or,
for a negated check, a false positive). Replaced every instance with
grep --quiet PATTERN <<< "${output}", which does not pipe at all.
|
||
|---|---|---|
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .wezel | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| debug.plist | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| Procfile | ||
| Procfile.web | ||
| README.md | ||
| renovate.json | ||
| REVIEWERS.conl | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
| typos.toml | ||
Important
Remove this line to confirm you've reviewed this PR before submitting.
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.