Joseph T. LyonsandBen Kunkle
5c4f9e57d8
Closes https://github.com/zed-industries/zed/issues/8968 This PR addresses the following scenario: 1. User's Zed polls for an update, finds one, and installs it 2. User doesn't immediately restart Zed, a new update is released, and the previous version of Zed would stop polling (ignoring the new update) 3. User eventually restarts Zed and is immediately prompted to install another update With this change, the auto-updater will continue polling for and installing new versions even after an initial update is found, reducing update prompts on restart. --- This PR does not address the following scenario: 1. User's Zed polls for an update, finds one, and installs it 2. Another update is released before the next scheduled polling interval 3. User restarts Zed and is immediately prompted to install the newer update Release Notes: - Improved the auto-updater to continue checking for updates even after finding and installing an initial update. This reduces situations where users are prompted to install another update immediately after restarting from a previous update. Co-authored-by: Ben Kunkle <Ben.kunkle@gmail.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.