From b4f373e0aeec04046321e1fead22fad59c2af095 Mon Sep 17 00:00:00 2001
From: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Date: Wed, 21 Oct 2026 03:50:48 -0400
Subject: [PATCH] Upgrading to 2.1 requires Beacon Web 2.1 (#39)

---
 docs/upgrading.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/docs/upgrading.md b/docs/upgrading.md
index 7858ad7..70b1df9 100644
--- a/docs/upgrading.md
+++ b/docs/upgrading.md
@@ -137,9 +137,11 @@ the flood jail's `maxretry` of 900 still sits above the new limit.
 ## Upgrading to 2.1
 
 Server 2.1.0 adds exact page cursors (`nextPageCursor` and `pageCursor`) to `/packets`, `/nodes`
-and `/observers`; see [Exact page cursors](api-contract.md#exact-page-cursors). The change is
-additive and the minimum web and app versions stay where they were, so older clients keep
-working. Pull Beacon Web 2.1 with the server.
+and `/observers`; see [Exact page cursors](api-contract.md#exact-page-cursors). The API change is
+additive, but server 2.1 requires Beacon Web 2.1 (`minWebVersion` 2.1.0): older web versions do not
+wait out the 503s that region, scope and advert pages answer while a read model is not ready, and
+they skip rows tied on a page boundary. Deploy Beacon Web 2.1 together with the server; an open
+tab on an older web version shows the reload screen. The minimum app version stays 2.0.0.
 
 Migrations `025` to `033` add two checks, four indexes and a statistics object to `packets`.
 Before deploying, run the [pre-deploy check](operations.md#before-deploying-a-release) and the