Skip to content
New issue

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

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

Already on GitHub? # to your account

Tracking issue for release notes of #135811: Make Miri aware of leaks of Box/Vec/String #137075

Closed
3 tasks
rustbot opened this issue Feb 15, 2025 · 1 comment
Closed
3 tasks
Labels
relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@rustbot
Copy link
Collaborator

rustbot commented Feb 15, 2025

This issue tracks the release notes text for #135811.

Steps

  • Proposed text is drafted by PR author (or team) making the noteworthy change.
  • Issue is nominated for release team review of clarity for wider audience.
  • Release team includes text in release notes/blog posts.

Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Make Miri aware of leaks of `Box`/`Vec`/`String`](https://github.com/rust-lang/rust/pull/135811)

Tip

Use the previous releases categories to help choose which one(s) to use.
The category will be de-duplicated with all the other ones by the release team.

More than one section can be included if needed.

Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
Otherwise leave it empty.

cc @nvzqz, @RalfJung -- origin issue/PR authors and assignees for starting to draft text

@rustbot rustbot added relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Feb 15, 2025
@fmease
Copy link
Member

fmease commented Feb 15, 2025

The PR was FCP-closed, not FCP-merged. A relnotes entry doesn't make sense. Closing as not planned.

@rust-lang/release I think it'd be a good idea to make rustbot ignore finished FCPs with disposition close or postpone.

@fmease fmease closed this as not planned Won't fix, can't repro, duplicate, stale Feb 15, 2025
@fmease fmease removed the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Feb 15, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants