MartinYe1234
b53b14d214
Removing the `Rule` variant from `MentionUri` in #58080 broke deserialization of any thread saved before the rules-to-skills migration. Loading one failed with `unknown variant `Rule``, making those threads inaccessible. This restores access without bringing back the rules feature: - Reintroduce a backward-compatible `Rule` mention variant so legacy threads deserialize again. - Preserve the original rule `id` through save/load so a thread re-saved by a newer build still loads on older Zed versions (and synthesize a valid placeholder when the id is missing). - Clicking a legacy rule mention now opens the skill the rule was migrated into, and shows a notification linking the Skills docs. On remote/collab projects the migrated file lives on the local machine, so it opens as a read-only buffer. If no matching skill exists, it does nothing. Closes https://github.com/zed-industries/zed/issues/58498 Closes AI-371 Release Notes: - Fixed old threads that mention Rules being inaccessible after Rules were migrated to Skills
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.