Two fixes make the cut here. The hydration failure is the one worth caring about — if your dev environment pulls pages from HTTP cache (common with certain proxy setups or aggressive service workers), the 16.2.x line was silently breaking hydration in ways that don't reproduce in prod, which is exactly the kind of bug that wastes a morning. The docs fix corrects an inaccuracy introduced with 16.2. Neither change affects production behavior. Patch releases in this cadence are routine, and this one is quiet enough that upgrading opportunistically is fine — no urgency unless you've hit the hydration issue.