Update RELEASES.md for 1.55.0 #87624
Conversation
rust-highfive
added
the
S-waiting-on-review
XAMPPRocky
added
the
T-release
There was a problem hiding this comment.
Hey I'm sorry, the rustdoc team has not been great about tagging PRs with relnotes as the land. I added a few just now - do you mind adding them to the release notes? https://github.com/rust-lang/rust/pulls?q=is%3Apr+is%3Amerged+label%3AT-rustdoc+label%3Arelnotes+milestone%3A1.55.0
|
I'm not an expert, but it looks great to me! |
RELEASES.md
Outdated
|
|
||
| Language | ||
| -------- | ||
| - [You can create bindings inside of a `@` bindings pattern.][85305] E.g. the |
There was a problem hiding this comment.
This landed into 1.56, per the milestone on the stabilization PR.
Mark-Simulacrum
force-pushed
the
master
branch
from
e9ec94f
to
d488de8
Compare
|
Hm, that seems to have not worked, weird, not sure what went wrong there. I'll open a new PR and r+ it in short order. |
…rk-Simulacrum Update RELEASES.md for 1.55.0 Reopening rust-lang#87624 after some edits and a force-push caused GitHub to close the PR.
…rk-Simulacrum Update RELEASES.md for 1.55.0 Reopening rust-lang#87624 after some edits and a force-push caused GitHub to close the PR.
|
@Mark-Simulacrum For future reference, https://gist.github.com/robertpainsi/2c42c15f1ce6dab03a0675348edd4e2c described how to reopen a PR after force pushing to it. |
|
@Aaron1011 That might be useful to link in forge somewhere, it seems to come up enough. |
…rk-Simulacrum Update RELEASES.md for 1.55.0 Reopening rust-lang#87624 after some edits and a force-push caused GitHub to close the PR.
Rendered
r? @Mark-Simulacrum
cc @rust-lang/release