Fix removed version numbers of doc_auto_cfg and doc_cfg_hide

[DJMcNab]

Tracking issue: #43781

The doc_auto_cfg and doc_cfg_hide features were removed in a recent nightly (by #138907).
I believe that the rustc version numbers at which the features were declared to be removed were incorrect, however, and should both be "1.92" (±1). As evidence in favour of this, the error we get from using this was:

error[E0557]: feature has been removed
  --> src/lib.rs:22:29
   |
22 | #![cfg_attr(docsrs, feature(doc_auto_cfg))]
   |                             ^^^^^^^^^^^^ feature has been removed
   |
   = note: removed in 1.58.0; see <https://github.com/rust-lang/rust/pull/138907> for more information
   = note: merged into `doc_cfg`

Note especially the "removed in 1.58" claim. Further evidence is found in the comment further up this file:

rust/compiler/rustc_feature/src/removed.rs

Lines 49 to 53 in 4ffeda1

	// Note that the version indicates when it got *removed*.
	// When moving an unstable feature here, set the version number to
	// `CURRENT RUSTC VERSION` with ` ` replaced by `_`.
	// (But not all features below do this properly; many indicate the
	// version they got originally added in.)

I've chosen 1.92 as that was the milestone which #138907 was added to.

cc @GuillaumeGomez

[rustbot]

r? @BoxyUwU

rustbot has assigned @BoxyUwU.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[DJMcNab]

The tidy check's requirement of using CURRENT_RUSTC_VERSION does now mean that the current version of this PR has a deadline of (whenever the next PR like #146636 is merged). That requirement seems to be not well-formed in this case, but I'm not certain about that.

Procedurally, do I need to now squash this PR? Is there a way to do that from the web, or will I need to clone locally?

Also hey Boxy!

[fmease]

Thanks! Yes, please squash, then I'll approve.

[fmease]

whenever the next PR like #146636 is merged

It happens earlier in the release process, namely when beta branches from master (cc https://forge.rust-lang.org/release/process.html#beta-pr). The PR you've linked is a bootstrap bump which just cherry-picks the previously created commit containing the placeholder replacements (cc https://forge.rust-lang.org/release/process.html#default-branch-bootstrap-update-tuesday).

Anyway, there's no rush; it'll take some time till the next beta bump. Both PRs will be part of 1.92, no worries :)

[rustbot]

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[DJMcNab]

@rustbot ready

cc @fmease I'm not sure of the process here - I can't request your review because you've never actually "reviewed" this PR

[fmease]

Thanks again! @bors r+ rollup

[bors]

📌 Commit 04ee991 has been approved by fmease

It is now in the queue for this repository.