Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release notes for 1.76 #120004

Merged
merged 1 commit into from
Feb 4, 2024
Merged

Release notes for 1.76 #120004

merged 1 commit into from
Feb 4, 2024

Conversation

Mark-Simulacrum
Copy link
Member

Cargo, library stabilizations and some cleanups, particularly to future compat, still pending.

cc @cuviper @rust-lang/release

@rustbot
Copy link
Collaborator

rustbot commented Jan 15, 2024

@Mark-Simulacrum: no appropriate reviewer found, use r? to override

@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 Jan 15, 2024
@Mark-Simulacrum
Copy link
Member Author

r? @cuviper

RELEASES.md Outdated Show resolved Hide resolved
RELEASES.md Show resolved Hide resolved
@Mark-Simulacrum
Copy link
Member Author

@bors r+ rollup p=1

@bors
Copy link
Contributor

bors commented Feb 3, 2024

📌 Commit 8f1573a has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors
Copy link
Contributor

bors commented Feb 3, 2024

🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 3, 2024
bors added a commit to rust-lang-ci/rust that referenced this pull request Feb 4, 2024
…iaskrgr

Rollup of 10 pull requests

Successful merges:

 - rust-lang#119543 (add avx512fp16 to x86 target features)
 - rust-lang#120004 (Release notes for 1.76)
 - rust-lang#120562 (Revert unsound libcore changes)
 - rust-lang#120566 (coverage: Use normal `edition:` headers in coverage tests)
 - rust-lang#120570 (Suggest changing type to const parameters if we encounter a type in the trait bound position)
 - rust-lang#120571 (Miscellaneous diagnostics cleanups)
 - rust-lang#120573 (Remove `BorrowckErrors::tainted_by_errors`)
 - rust-lang#120592 (Remove unnecessary `.to_string()`/`.as_str()`s)
 - rust-lang#120610 (hir: Remove the generic type parameter from `MaybeOwned`)
 - rust-lang#120616 (Fix ICE on field access on a tainted type after const-eval failure)

Failed merges:

 - rust-lang#120569 (coverage: Improve handling of function/closure spans)

r? `@ghost`
`@rustbot` modify labels: rollup
bors added a commit to rust-lang-ci/rust that referenced this pull request Feb 4, 2024
…iaskrgr

Rollup of 10 pull requests

Successful merges:

 - rust-lang#119543 (add avx512fp16 to x86 target features)
 - rust-lang#120004 (Release notes for 1.76)
 - rust-lang#120562 (Revert unsound libcore changes)
 - rust-lang#120566 (coverage: Use normal `edition:` headers in coverage tests)
 - rust-lang#120570 (Suggest changing type to const parameters if we encounter a type in the trait bound position)
 - rust-lang#120571 (Miscellaneous diagnostics cleanups)
 - rust-lang#120573 (Remove `BorrowckErrors::tainted_by_errors`)
 - rust-lang#120592 (Remove unnecessary `.to_string()`/`.as_str()`s)
 - rust-lang#120610 (hir: Remove the generic type parameter from `MaybeOwned`)
 - rust-lang#120616 (Fix ICE on field access on a tainted type after const-eval failure)

Failed merges:

 - rust-lang#120569 (coverage: Improve handling of function/closure spans)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 98d0d45 into rust-lang:master Feb 4, 2024
11 checks passed
@rustbot rustbot added this to the 1.78.0 milestone Feb 4, 2024
rust-timer added a commit to rust-lang-ci/rust that referenced this pull request Feb 4, 2024
Rollup merge of rust-lang#120004 - Mark-Simulacrum:relnotes-1.76, r=Mark-Simulacrum

Release notes for 1.76

Cargo, library stabilizations and some cleanups, particularly to future compat, still pending.

cc `@cuviper` `@rust-lang/release`
@deltragon
Copy link
Contributor

Not sure where to best ask this - I was wondering if this should explicitly point out that win7 support is being dropped from the tier 1 windows target, in addition to the new separate win7 target?
For example, in 1.75, the compatibility notes called out the freebsd baseline being raised, this seems like a parallel to that to me.
(Unless I missed something and the tier 1 change was delayed to a later release)

@Mark-Simulacrum Mark-Simulacrum deleted the relnotes-1.76 branch February 5, 2024 12:39
@Mark-Simulacrum
Copy link
Member Author

Did a PR dropping that support actually land? The platform support file and quick skim of history doesn't show that we have declared the drop of support. So I think the earliest it will likely happen now is 1.78 (current nightly).

@slanterns
Copy link
Contributor

slanterns commented Feb 5, 2024

Per rust-lang/compiler-team#651, the decision is to drop the support in 1.76, and we announced it in the 1.72 release post (although #115141 has not be merged yet.)

@Mark-Simulacrum
Copy link
Member Author

We've already built artifacts etc, so I think it'll slip to 1.77 at least, this doesn't seem like something worth rebuilding artifacts for.

@ChrisDenton
Copy link
Member

Yes, sorry, it's fine to let it slip to 1.77. The intent was to have a blog post out earlier explaining things (and the new win7 target) but I've had a busy new year and not been on top of things. In retrospect it was silly to schedule it so early in the year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. 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.

9 participants