Moves `cloud_api_client` off the `zed-industries/yawc` fork pin (`71a452f`) to the upstream crates.io release, `yawc` 0.4.2. The fork's only commit beyond upstream was an earlier version of a wasm connect fix. Upstream shipped a more complete fix in 0.4.0 ([infinitefield/yawc@f1c6317](https://github.com/infinitefield/yawc/commit/f1c6317eff64a01433aad683280e22ddff4f9c3f)): - `connect` settles on the browser's `open`, `error`, or `close` event. - The wasm `WebSocket` owns its event handlers instead of leaking them with `Closure::forget`. - `Drop` unregisters the handlers and calls `close()`, including when the connect future is dropped mid-handshake. That last point matters for the web Cloud client, which drops a pending connect after 30 seconds. With the fork, the abandoned browser socket kept handshaking indefinitely. Delta hit the same leak in its web client and has already moved to 0.4.2. The other changes between the fork and 0.4.2 are native-only: opt-in HTTP/2 WebSockets, SOCKS5 proxy support, and a deflate decompression fix. The APIs `cloud_api_client` uses are unchanged. The lock file also picks up `send_wrapper` and bumps `hyper` to 1.11 and `h2` to 0.4.19, which `yawc` 0.4.2 requires. Checked with `cargo check -p cloud_api_client` for native and `wasm32-unknown-unknown`. Release Notes: - N/A
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.