Skip to content

docs: say the MSRV the manifest actually declares - #84

Merged
adityak74 merged 1 commit into
mainfrom
docs/msrv-drift
Aug 22, 2026
Merged

docs: say the MSRV the manifest actually declares#84
adityak74 merged 1 commit into
mainfrom
docs/msrv-drift

Conversation

@adityak74

Copy link
Copy Markdown
Contributor

CLAUDE.md and AGENTS.md both said MSRV is 1.82. The root
Cargo.toml says rust-version = "1.95", and the msrv CI job pins that
exact toolchain.

The manifest is right and the docs were wrong. This is not a number that
drifted ahead of reality; 1.82 has not built this workspace for a while. The
msrv job's own comment records why it exists:

the declared floor sat at 1.82 while the dependency tree had walked to 1.95:
cargo +1.82 check --workspace --locked failed on hashbrown wanting
Cargo's edition2024 feature, and no build ever went red.

That job was added to stop the manifest drifting. Nobody updated the two
files that repeat the number in prose.

Why this one is worth a commit

It is the line somebody reads before deciding whether a standard library API
is available to them. A floor stated thirteen versions too low steers work
away from things that are in fact usable, and it does so invisibly, because
the wrong answer still compiles.

It already cost something. On the on-device search branch, slice::as_chunks
looked out of reach and an #[allow] looked like the safer option. It has
been stable since 1.88, comfortably under the real floor, and the direct fix
was available the whole time.

The change

Both files get the same replacement, which is the standing rule for this
pair. The new wording names rust-version and the msrv job as the source
of truth and says to read the manifest if the two ever disagree again, so the
next drift is a doc bug somebody can spot rather than a mystery.

Documentation only. No code, no manifests, no CI.

https://claude.ai/code/session_01KGPVQ8wUG7h36zashWYCp4

Both instruction files said MSRV is 1.82. The root Cargo.toml has said
1.95 since the dependency tree walked past 1.82, and the msrv CI job
pins that exact toolchain, so the docs have been wrong rather than
merely out of date: 1.82 has not built this workspace for a while.

This is not a harmless stale number. It is the line an agent reads
before deciding whether a standard library API is available, and a floor
stated thirteen versions too low steers work away from things that are
in fact usable. It cost a real detour on the on-device search branch,
where as_chunks, stable since 1.88, looked out of reach.

Both files carry the same wording, which is the rule for this pair, and
the new text points at the manifest as the answer so the next drift is
a doc bug and not a mystery.

Claude-Session: https://claude.ai/code/session_01KGPVQ8wUG7h36zashWYCp4
@adityak74
adityak74 merged commit 0f58b97 into main Aug 22, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant