Ruben Fricke
d3f051031f
Without this fix, the zed.dev server doesn't recognize the version with metadata and redirects to /releases, which defaults to the Stable channel, so Preview users end up seeing Stable release notes. Closes #47539 Changes: - Strip pre and build metadata from the semver version in release_notes_url before constructing the path, so the URL becomes /releases/preview/0.218.0 instead of /releases/preview/0.218.0-beta.1+preview.131.68e98a53. - Standardized the ordering of pre/build clearing to pre-first across all 4 call sites (2 were build-first). Open question: With this fix, the URL now points to the specific version you're running (e.g. /releases/preview/0.218.0). An alternative would be to link to /releases/preview (no version) so users can see all Preview releases, including ones newer than what they have installed. I went with per-version linking since it matches the existing intent of the code, but happy to change it if the team prefers the other approach. Release Notes: - Fixed "View Release Notes" in Preview/Stable opening the wrong release channel page due to build metadata in the URL.
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 issue)
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
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.