3bbdc546ec
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [time](https://time-rs.github.io) ([source](https://redirect.github.com/time-rs/time)) | workspace.dependencies | patch | `0.3.37` -> `0.3.40` | --- ### Release Notes <details> <summary>time-rs/time (time)</summary> ### [`v0.3.40`](https://redirect.github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0340-2025-03-18) [Compare Source](https://redirect.github.com/time-rs/time/compare/v0.3.39...v0.3.40) ##### Added - Visibility modifiers may now be added to the `mod` generated by `time::sere::format_description!`. ### [`v0.3.39`](https://redirect.github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0339-2025-03-06) [Compare Source](https://redirect.github.com/time-rs/time/compare/v0.3.38...v0.3.39) ##### Fixed - Doc tests run successfully with the default feature set. - wasm builds work again. Both of these were regressions in v0.3.38 and are now checked in CI. ### [`v0.3.38`](https://redirect.github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0338-2025-03-05) [Compare Source](https://redirect.github.com/time-rs/time/compare/v0.3.37...v0.3.38) ##### Added - The `[year]` component (in format descriptions) now supports a `range` modifier, which can be either `standard` or `extended`. The default is `extended` for backwards compatibility. This is intended as a manner to opt *out* of the extended range when the `large-dates` feature is enabled. When the `large-dates` feature is not enabled, the modifier has no effect. - `UtcDateTime`, which is semantically equivalent to an `OffsetDateTime` with UTC as its offset. The advantage is that it is the same size as a `PrimitiveDateTime` and has improved operability with well-known formats. As part of this, there were some other additions: - `utc_datetime!` macro, which is similar to the `datetime!` macro but constructs a `UtcDateTime`. - `PrimitiveDateTime::as_utc` - `OffsetDateTime::to_utc` - `OffsetDateTime::checked_to_utc` - `time::serde::timestamp::milliseconds_i64`, which is a module to serialize/deserialize timestamps as the Unix timestamp. The pre-existing module does this as an `i128` where an `i64` would suffice. This new module should be preferred. ##### Changed - `error::Format` has had its `source()` implementation changed to no longer return a boxed value from the `ComponentRange` variant. If you were explicitly expecting this, you will need to update your code. The method API remains unchanged. - `[year repr:century]` supports single-digit values. - All `format_into` methods accept `?Sized` references. ##### Miscellaneous - Some non-exhaustive enum variants that are no longer used have been modified to be statically proven as uninhabited. The relevant fields are doc-hidden and not semver-guaranteed to remain as such, though it is unlikely to change. - An unnecessary check when parsing RFC 2822 has been removed. - Various methods have had their implementations changed, resulting in significant performance gains. Among the methods changed are - `util::is_leap_year` - `util::weeks_in_year` - `Month::length` - `Date::to_calendar_date` - `Date::month` - `Date::day` - `Date::from_julian_day` - `Date::to_julian_day` - other methods that call into these methods </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.