[ntdatt812]

Closes #5781.

The defect

All six READMEs told contributors to install Rust 1.93.0. The pin says otherwise, and its own comment says why:

# rust-toolchain.toml
# Rust 1.96 is required by rusqlite 0.40 / libsqlite3-sys 0.38: their build
# scripts use the `cfg_select!` macro, stabilized in 1.96 ...
channel = "1.96.1"

CONTRIBUTING.md:41 already stated 1.96.1, so the two contributor-facing documents disagreed with each other as well as with the pin. A new contributor following the README hit a cfg_select! build failure in libsqlite3-sys on their first cargo check — before writing a line of code.

Verified in-tree

$ grep ^channel rust-toolchain.toml
channel = "1.96.1"

$ grep -n '1\.9[0-9]\.[0-9]' CONTRIBUTING.md
41:| Rust | `1.96.1` from rust-toolchain.toml | ...
62:rustup toolchain install 1.96.1 --profile minimal

$ grep -rn 'Rust 1\.9[0-9]\.[0-9]' README.md docs/README.*.md
README.md:161            ... Rust 1.93.0 ...
docs/README.de.md:158    ... Rust 1.93.0 ...
docs/README.ja-JP.md:158 ... Rust 1.93.0 ...
docs/README.ko.md:158    ... Rust 1.93.0 ...
docs/README.ur-pk.md:204 ... Rust 1.93.0 ...
docs/README.zh-CN.md:158 ... Rust 1.93.0 ...

The change

Six files, one substitution each, nothing else touched — the surrounding prose and every translation are unchanged. grep -rc '1\.93\.0' over the six files returns nothing afterwards.

Summary by CodeRabbit

• Documentation
  • Updated contribution instructions to require Rust 1.96.1 instead of 1.93.0.
  • Synchronized the prerequisite across English, German, Japanese, Korean, Urdu, and Simplified Chinese documentation.

[tinysweeper]

tinysweeper found nothing blocking. Approving.

$0.0000 · 0 in / 0 out

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2aa8cd28-3e98-4bf0-bce4-ed34c163d45d

📥 Commits

Reviewing files that changed from the base of the PR and between 77fddf5 and ac20235.

📒 Files selected for processing (6)

• README.md
• docs/README.de.md
• docs/README.ja-JP.md
• docs/README.ko.md
• docs/README.ur-pk.md
• docs/README.zh-CN.md

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The contributor instructions in the English, German, Japanese, Korean, Urdu, and Chinese READMEs now require Rust 1.96.1 instead of Rust 1.93.0.

Changes

Rust prerequisite documentation

Layer / File(s)	Summary
Update contributor prerequisites README.md, docs/README.de.md, docs/README.ja-JP.md, docs/README.ko.md, docs/README.ur-pk.md, docs/README.zh-CN.md	All six README files now specify Rust 1.96.1. Other documented prerequisites remain unchanged.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to ac202

This localized documentation-only change aligns contributor instructions with the repository's pinned Rust toolchain, with no actionable merge-blocking risk remaining after normal checks and review.

Suggested reviewers: senamakel

Poem

A rabbit checks the Rusty guide,
Six README paths now match inside.
One point nine six, one, bright and clear,
No mismatched version hiding here.
Hop, build, and onward we cheer!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: documenting the Rust version pinned by the toolchain.
Linked Issues check	✅ Passed	The PR updates all six README files from Rust 1.93.0 to Rust 1.96.1. This satisfies issue #5781 and aligns the documentation with the pinned toolchain and CONTRIBUTING.md.
Out of Scope Changes check	✅ Passed	All six one-line documentation changes directly support issue #5781. No unrelated changes are reported.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)

Warning

Your free Security trial is over. An organization admin can activate billing to continue.

---

_{Comment @coderabbitai help to get the list of available commands.}

[M3gA-Mind]

Maintainer triage pass — review only, no changes pushed, not an approval.

This one is ready as far as I can tell. MERGEABLE, PR CI Gate green, every other check pass or skipping, no unresolved review threads.

I re-checked the claim against current main rather than taking the diff on trust:

$ git show upstream/main:rust-toolchain.toml
channel = "1.96.1"

and the six files this PR edits are exactly the six on main that still name the old version — no seventh got missed:

$ git grep -n "Rust 1\.9" upstream/main -- README.md docs/README*.md CONTRIBUTING.md CONTRIBUTING-BEGINNERS.md
README.md:160  docs/README.de.md:157  docs/README.ja-JP.md:157
docs/README.ko.md:157  docs/README.ur-pk.md:203  docs/README.zh-CN.md:157

All six say 1.93.0; all six are in the diff. The pin has moved twice since that number was written, so this is a real inaccuracy in the first instruction a new contributor follows, not a cosmetic bump.

Nothing needed from you. Flagging it to the maintainers as ready to merge.