rustdoc CURRENT_RUSTC_VERSION shows incorrect version between version bump and stage0 bump
Open
Nobody has claimed this yet.
A-docs
C-bug
T-bootstrap
T-rustdoc
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Items marked with the stability attribute and CURRENT_RUSTC_VERSION will show the wrong version in nightly rustdoc output in between the version bump and the stage0 bump. That means in this sequence:
- Item gets marked with
CURRENT_RUSTC_VERSION. Example, on nightly the current rust version is 1.80, which is what rustdoc shows. - Version is bumped example bumps to 1.81.
- Nightly docs for
CURRENT_RUSTC_VERSIONmarked items now show 1.81 when they should say 1.80. - Stage0 is bumped, and CURRENT_RUSTC_VERSION placeholders get replaced example. The item is now correctly marked 1.80.
This can be confusing since there can be a window of several days where the wrong version is displayed.
Contributor 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.
Research direction
Start by tracing how rustdoc handles CURRENT_RUSTC_VERSION during the version bump and stage0 bump sequence, using the two referenced pull requests as context. Reproduce the nightly output during that interval and confirm that marked items retain the correct version after the version bump; done means the misleading multi-day window is eliminated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100