Skip to content

Add relnotes for 1.100 - #165522

Open
BoxyUwU wants to merge 5 commits into
rust-lang:mainfrom
BoxyUwU:relnotes_1_100
Open

BoxyUwU wants to merge 5 commits into
rust-lang:mainfrom
BoxyUwU:relnotes_1_100

Conversation

@BoxyUwU

@BoxyUwU BoxyUwU commented Nov 5, 2026

Copy link
Copy Markdown
Member

r? cuviper

cc @rust-lang/release

@rustbot

rustbot commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

RELEASES.md was changed. Upon merging, each section will be automatically synced with its corresponding GitHub releases, but only from the main branch.

If it's not already the case, make sure to also merge the changes in the main branch.

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-release Relevant to the release subteam, which will review and decide on the PR/issue. labels Nov 5, 2026
Comment thread RELEASES.md Resolved
@BoxyUwU

BoxyUwU commented Nov 5, 2026

Copy link
Copy Markdown
Member Author

@rustbot ping relnotes-interest-group

@rustbot

rustbot commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

Hi relnotes-interest-group, this issue/PR could use some help in reviewing /
adjusting release notes. Could you take a look if available? Thanks <3

cc @alex-semenyuk @jieyouxu @joshtriplett @lcnr @traviscross @weihanglo

@weihanglo weihanglo left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for cargo part.

View changes since this review

Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
Comment thread RELEASES.md Resolved
BoxyUwU and others added 3 commits November 6, 2026 11:10
Co-authored-by: alexey semenyuk <alexsemenyuk88@gmail.com>
Co-authored-by: Kevin Reid <kpreid@switchb.org>
Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com>
Co-authored-by: Tim (Theemathas) Chirananthavat <theemathas@gmail.com>
Comment thread RELEASES.md
Comment on lines +105 to +108
- Introduced Cargo's own linting system: some Cargo warnings are now emitted as lints that users can control in the `[lints.cargo]` table. This includes a new built-in unused dependency check via the `cargo::unused_dependencies` lint. [docs](https://doc.rust-lang.org/nightly/cargo/reference/lints.html) [#17298](https://github.com/rust-lang/cargo/pull/17298)
- Introduced minimum publish age configurations, also known as dependency cooldowns. When the relevant config is set, the resolver ignores versions published more recently than that, unless they are already in `Cargo.lock`. ([RFC 3923](https://rust-lang.github.io/rfcs/3923-cargo-min-publish-age.html)) [docs](https://doc.rust-lang.org/nightly/cargo/reference/resolver.html#publish-age) [#17335](https://github.com/rust-lang/cargo/pull/17335)
- cargo-install: now uses the existing lockfile in the `.crate` tarball by default. `--locked` in cargo install becomes a no-op. [#17388](https://github.com/rust-lang/cargo/pull/17388)
- Cargo now uses a new directory layout for intermediate build artifacts. Tools that inspect the build directory may need to use [Cargo’s JSON messages](https://doc.rust-lang.org/nightly/cargo/reference/external-tools.html#json-messages) to locate build artifacts instead of relying on the build directory layout. The layout is not a stable interface and is subject to change. ([build cache doc](https://doc.rust-lang.org/nightly/cargo/reference/build-cache.html)) [#17354](https://github.com/rust-lang/cargo/pull/17354)

@cuviper cuviper Nov 7, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use stable doc links.

Suggested change
- Introduced Cargo's own linting system: some Cargo warnings are now emitted as lints that users can control in the `[lints.cargo]` table. This includes a new built-in unused dependency check via the `cargo::unused_dependencies` lint. [docs](https://doc.rust-lang.org/nightly/cargo/reference/lints.html) [#17298](https://github.com/rust-lang/cargo/pull/17298)
- Introduced minimum publish age configurations, also known as dependency cooldowns. When the relevant config is set, the resolver ignores versions published more recently than that, unless they are already in `Cargo.lock`. ([RFC 3923](https://rust-lang.github.io/rfcs/3923-cargo-min-publish-age.html)) [docs](https://doc.rust-lang.org/nightly/cargo/reference/resolver.html#publish-age) [#17335](https://github.com/rust-lang/cargo/pull/17335)
- cargo-install: now uses the existing lockfile in the `.crate` tarball by default. `--locked` in cargo install becomes a no-op. [#17388](https://github.com/rust-lang/cargo/pull/17388)
- Cargo now uses a new directory layout for intermediate build artifacts. Tools that inspect the build directory may need to use [Cargo’s JSON messages](https://doc.rust-lang.org/nightly/cargo/reference/external-tools.html#json-messages) to locate build artifacts instead of relying on the build directory layout. The layout is not a stable interface and is subject to change. ([build cache doc](https://doc.rust-lang.org/nightly/cargo/reference/build-cache.html)) [#17354](https://github.com/rust-lang/cargo/pull/17354)
- Introduced Cargo's own linting system: some Cargo warnings are now emitted as lints that users can control in the `[lints.cargo]` table. This includes a new built-in unused dependency check via the `cargo::unused_dependencies` lint. [docs](https://doc.rust-lang.org/stable/cargo/reference/lints.html) [#17298](https://github.com/rust-lang/cargo/pull/17298)
- Introduced minimum publish age configurations, also known as dependency cooldowns. When the relevant config is set, the resolver ignores versions published more recently than that, unless they are already in `Cargo.lock`. ([RFC 3923](https://rust-lang.github.io/rfcs/3923-cargo-min-publish-age.html)) [docs](https://doc.rust-lang.org/stable/cargo/reference/resolver.html#publish-age) [#17335](https://github.com/rust-lang/cargo/pull/17335)
- cargo-install: now uses the existing lockfile in the `.crate` tarball by default. `--locked` in cargo install becomes a no-op. [#17388](https://github.com/rust-lang/cargo/pull/17388)
- Cargo now uses a new directory layout for intermediate build artifacts. Tools that inspect the build directory may need to use [Cargo’s JSON messages](https://doc.rust-lang.org/stable/cargo/reference/external-tools.html#json-messages) to locate build artifacts instead of relying on the build directory layout. The layout is not a stable interface and is subject to change. ([build cache doc](https://doc.rust-lang.org/stable/cargo/reference/build-cache.html)) [#17354](https://github.com/rust-lang/cargo/pull/17354)

View changes since the review

Comment thread RELEASES.md
- [`impl<T: Allocator, A: Allocator> Allocator for Box<T, A>`](https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-Box%3CT,+A%3E)
- [`impl<A: Allocator> Allocator for &mut A`](https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-%26mut+A)
- [`impl<T: Allocator, A: Allocator> Allocator for Arc<T, A>`](https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-Arc%3CT,+A%3E)
- [`impl<T: Allocator, A: Allocator> Allocator for Rc<T, A>`](https://doc.rust-lang.org/beta/std/alloc/trait.Allocator.html#impl-Allocator-for-Rc%3CT,+A%3E)

@cuviper cuviper Nov 7, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [`impl<T: Allocator, A: Allocator> Allocator for Rc<T, A>`](https://doc.rust-lang.org/beta/std/alloc/trait.Allocator.html#impl-Allocator-for-Rc%3CT,+A%3E)
- [`impl<T: Allocator, A: Allocator> Allocator for Rc<T, A>`](https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-Rc%3CT,+A%3E)

View changes since the review

Comment thread RELEASES.md
- [`impl<T: Allocator, A: Allocator> Allocator for Rc<T, A>`](https://doc.rust-lang.org/beta/std/alloc/trait.Allocator.html#impl-Allocator-for-Rc%3CT,+A%3E)
- [`Box::new_in`](https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.new_in)
- [`Box::from_raw_in`](https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.from_raw_in)
- [`Box::from_non_null_in`](https://doc.rust-lang.org/beta/std/boxed/struct.Box.html#method.from_non_null_in)

@cuviper cuviper Nov 7, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [`Box::from_non_null_in`](https://doc.rust-lang.org/beta/std/boxed/struct.Box.html#method.from_non_null_in)
- [`Box::from_non_null_in`](https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.from_non_null_in)

View changes since the review

Comment thread RELEASES.md
- [`Child::main_thread_handle`](https://doc.rust-lang.org/stable/std/os/windows/process/trait.ChildExt.html#tymethod.main_thread_handle)
- [`impl Default for std::sync::Once`](https://doc.rust-lang.org/stable/std/sync/struct.Once.html#impl-Default-for-Once)
- [`bool::toggle`](https://doc.rust-lang.org/stable/std/primitive.bool.html#method.toggle)
- [`Box::take`](https://doc.rust-lang.org/beta/std/boxed/struct.Box.html#method.take)

@cuviper cuviper Nov 7, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [`Box::take`](https://doc.rust-lang.org/beta/std/boxed/struct.Box.html#method.take)
- [`Box::take`](https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.take)

View changes since the review

Comment thread RELEASES.md
Comment on lines +88 to +89
- [`core::mem::DropGuard`](https://doc.rust-lang.org/stable/core/mem/struct.DropGuard.html)
- [`std::mem::conjure_zst`](https://doc.rust-lang.org/stable/std/mem/fn.conjure_zst.html)

@cuviper cuviper Nov 7, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's consistently use core::mem here (or we could go the other way)

Suggested change
- [`core::mem::DropGuard`](https://doc.rust-lang.org/stable/core/mem/struct.DropGuard.html)
- [`std::mem::conjure_zst`](https://doc.rust-lang.org/stable/std/mem/fn.conjure_zst.html)
- [`core::mem::DropGuard`](https://doc.rust-lang.org/stable/core/mem/struct.DropGuard.html)
- [`core::mem::conjure_zst`](https://doc.rust-lang.org/stable/core/mem/fn.conjure_zst.html)

View changes since the review

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-release Relevant to the release subteam, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants