-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Add release notes for 1.80 #127083
Add release notes for 1.80 #127083
Conversation
35a552d
to
4e12172
Compare
@bors r+ rollup |
…lacrum Add release notes for 1.80 cc `@rust-lang/release` r? `@Mark-Simulacrum` I tended to err on the side of leaving more stuff in since I don't have a perfect idea of what should or should not be in the release notes right now.
Hmm, #127340 should be in the release notes as an accepted regression due to a soundness fix. While it only affects two crates, the pattern it breaks is more likely to be an issue in binaries. |
wait, I'm not sure if T-libs accepted it lol nm |
wait yes they did. |
@bors r- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or you can tell me to buzz off and r+ this again if you don't wanna include this, that's fine too.
Co-authored-by: Jubilee <[email protected]>
@bors r=Mark-Simulacrum,workingjubilee |
…iaskrgr Rollup of 5 pull requests Successful merges: - rust-lang#127083 (Add release notes for 1.80) - rust-lang#127322 (handle ci-rustc incompatible options during config parse) - rust-lang#127697 (use std for file mtime and atime modifications) - rust-lang#127704 (Fix minor typos in std::process doc on Win argv) - rust-lang#127710 (clarify the meaning of the version number for accepted/removed features) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#127083 - BoxyUwU:relnotes_1_80, r=Mark-Simulacrum,workingjubilee Add release notes for 1.80 cc `@rust-lang/release` r? `@Mark-Simulacrum` I tended to err on the side of leaving more stuff in since I don't have a perfect idea of what should or should not be in the release notes right now.
cc @rust-lang/release
r? @Mark-Simulacrum
I tended to err on the side of leaving more stuff in since I don't have a perfect idea of what should or should not be in the release notes right now.