Analysis
It reads what you merge.
Most stale docs go unnoticed because nobody rereads the whole site after every merge. uptodate does, comparing the change against each page to find the ones it made inaccurate.
a1f30c2the change you merged
src/auth/session.ts-const SESSION_TTL = days(14);+const SESSION_TTL = days(30);
uptodate ranks every page, biased toward including it
- authentication.mdxSelected
- sessions.mdxSelected
- quickstart.mdxSkipped
- billing.mdxSkipped
01
Isolate the code that actually changed
uptodate looks at the range you merged and sets aside everything inside your docs folder. What is left is the code your documentation describes, and nothing else.
02
Rank every page against that change
It reads through your Markdown and MDX pages and weighs which ones the change could have made wrong. It leans toward including a page, so a borderline match gets checked rather than missed.
A page you never thought to open is the one that was quietly wrong. Ranking every page each time is how uptodate catches it.