renovate[bot]andrenovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2bf9c472bd
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [oo7](https://redirect.github.com/bilelmoussaoui/oo7) | dependencies | patch | `0.4.1` -> `0.4.3` | --- ### Release Notes <details> <summary>bilelmoussaoui/oo7 (oo7)</summary> ### [`v0.4.3`](https://redirect.github.com/bilelmoussaoui/oo7/releases/tag/0.4.3) [Compare Source](https://redirect.github.com/bilelmoussaoui/oo7/compare/0.4.2...0.4.3) - [cli: Add custom keyring file support](https://redirect.github.com/bilelmoussaoui/oo7/commit/248d96f225802cbed69c4fcc186ece85ec2bc1f8) - [dbus/secret: Workaround gnome-keyring being non-spec compliant](https://redirect.github.com/bilelmoussaoui/oo7/commit/cac94b502f0ebff276e43fbc4f1987ea77432a9d) - [client: Deprecate Keyring::with_broken_item_cleanup](https://redirect.github.com/bilelmoussaoui/oo7/commit/cce024ba64cdfa74eb2f21a6cdffda79ed5a2fe1) - [cli: Add a new argument for listing all items](https://redirect.github.com/bilelmoussaoui/oo7/commit/88f56041474d6618c251dd60e50ccc2bd056c702) ### [`v0.4.2`](https://redirect.github.com/bilelmoussaoui/oo7/releases/tag/0.4.2) #### What's Changed Relax the condition when validating the file backend keyring secret and provide various APIs to allow the developer to recover the non-broken items in a keyring or delete the broken ones. The root cause of the issue has not been identified but at least apps will continue to work as normal if the developer uses `Keyring::with_broken_item_cleanup` instead of `Keyring::new`. More details can be found in [#​207](https://redirect.github.com/bilelmoussaoui/oo7/issues/207) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "after 3pm on Wednesday" in timezone America/New_York, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- Release Notes: - N/A <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMDcuMSIsInVwZGF0ZWRJblZlciI6IjM5LjIwNy4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
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.