ᴀᴍᴛᴏᴀᴇʀ
67b52f378f
After setting a custom icon on macOS, an `Icon\r` file is generated in the application's root directory to store the custom icon metadata. Currently, the update process uses `rsync -av --delete`, which removes this `Icon\r` file and causes the custom icon to revert to the default blue folder. This PR adds the `--exclude 'Icon?'` parameter to ensure the file is preserved during updates. Closes #26639 , Closes #29900. Since I cannot trigger the auto-update mechanism manually, I mounted the latest Zed disk image and simulated the update by executing the rsync command in the terminal to verify the fix. <img width="2254" height="1596" alt="图片" src="https://github.com/user-attachments/assets/26660fa4-447f-427a-b2dd-e6280ce3d42d" /> Before you mark this PR as ready for review, make sure that you have: - [x] Added a solid test coverage and/or screenshots from doing manual testing - [x] Done a self-review taking into account security and performance aspects - [x] Aligned any UI changes with the [UI checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) Release Notes: - Fixed an issue where custom macOS app icons would revert to default blue folders after an update.
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.