Tracking issue for release notes of #164028: Add a future incompat warning for #[no_link]
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github, rust
- Domain
- documentation, release
Research direction
Read the release notes guidance linked in the issue and review the proposed Compatibility Notes entry for PR #164028. Confirm the correct release note category and whether an additional compatibility note is needed, then update the release notes text; the blog section should remain empty unless the change warrants a blog post.
Written by the indexing model from the issue text.
Description
This issue tracks the release notes text for #164028.
cc @bjorn3, @JonathanBrouwer -- original issue/PR authors and assignees for drafting text
See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.
Release notes text
This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:
- Does this need an additional compat notes section?
- Was this a libs stabilization that should have additional headers to list new APIs under
Stabilized APIsandConst Stabilized APIs?
# Compatibility Notes
- [Add a future incompat warning for #[no_link]](https://github.com/rust-lang/rust/pull/164028)
[!TIP]
Use the previous releases for inspiration on how to write the release notes text and which categories to pick.
Release blog section
If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.
[!NOTE]
If a blog post section is required the
release-blog-postlabel should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.
- Dominant language
- Rust
- Stars
- 121k
- Forks
- 18.7k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 536
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rust-lang/rust
-
relnotes relnotes-needs-review relnotes-tracking-issue T-libs
Difficulty 1/5 Under an hour Newbie friendliness 68/100
rust-lang/rust#164919 · 1 comment ·
Maintainers usually reply within 1 day
-
relnotes relnotes-tracking-issue T-libs
Difficulty 1/5 Under an hour Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
A-patterns F-guard_patterns relnotes relnotes-needs-review relnotes-tracking-issue T-compiler T-lang
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
relnotes relnotes-needs-review relnotes-tracking-issue T-compiler T-lang
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
A-docs T-libs T-opsem
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
rust-lang/rust#164818 · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
documentation enhancement SIEM
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ADORSYS-GIS/wazuh-agent-status#265 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
manuscript-lang/manuscript#1629 ·
Maintainers usually reply within 1 day
-
autofixer: follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tursodatabase/turso#10885 ·
Maintainers usually reply within 1 day
-
🐞 bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nannou-org/gantz#475 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100