Piotr Osiewicz
ceeaeae5b3
## Summary Move `check_postgres_and_protobuf_migrations` from the existing 16-vCPU / 32-GiB Linux runner to the existing 8-vCPU / 16-GiB runner. The job handles Git history and Buf compatibility, lint, and formatting checks; its commands, triggers, and coverage remain unchanged. This reduces its concurrent CPU and memory allocation by half. Namespace observations from September 11–14 covered 224 runs, with a typical job duration of 37 seconds and maximum observed RAM around 1.5 GiB. The p95 of per-run peak CPU usage was about 7.7 cores, so CI runtime on the smaller profile should be checked rather than assuming identical performance. Updated the Rust workflow generator and regenerated the YAML. No other jobs are changed. ## Validation - `cargo xtask workflows` - `cargo fmt -p xtask -- --check` - `git diff --check` - Full diff reviewed: two files, only the runner selection changed. - Actual migration check on the smaller runner awaits CI. Release Notes: - N/A
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.