flags

Follow-up to the review request on : check whether the function returned by should anywhere, and add it where it is missing. Result: nothing was missing. Every path that needs request data already reads it, and the paths that do not read it must stay prerenderable. So this PR contains no behavior change — it documents the guarantee and locks it in with tests, since it is the kind of thing a future refactor can silently drop. The audit is "only necessary when dynamic rendering is required and common Request-time APIs are not used". Path by path: Adding to the App Router paths would also mean importing , which deliberately avoids at the top level so it keeps working in Pages Router, plus one more awaited promise per evaluation — for no change in behavior. What is in the PR Comments at each branch in , , , and the precomputed branch of , recording why is or is not appropriate there. Unit tests () asserting which paths touch / and which must not — including cache hits, overrides, bulk evaluation, precomputed reads, and Pages Router. e2e coverage in and : a new route rendering , a flag whose ignores the request and returns a new value on every evaluation. If the SDK were not reading the request, the page would be baked at build time. Next 15 build reports the route as , while stays . Next 16 (Cache Components) reports it as and streams the flag outside the static shell. Both suites assert two requests return different values. The Next 16 build is the sharpest check of the three. Replacing the flag with a bare in the same component fails the build with: Route "/tmp-counterfactual" used before accessing either uncached data (e.g. ) or Request data (e.g. , , , and ). With the flag, the build passes — Next.js itself confirms the SDK read Request data before ran. So if this guarantee ever regresses, stops building. Docs**: a "Dynamic rendering" section under in the API reference, and the same note in the flags-sdk skill, so nobody adds in front of a flag evaluation. Verification : 126 unit tests pass, clean. e2e: 7/7 pass. e2e: the new test passes. One pre-existing failure, , expects , which Next 16.2.12 does not emit for that route — reproduced on a pristine checkout, so it is unrelated to this change. clean on all touched files. No changeset: no published package changes behavior.

This is to primarily update the lock file and enforce 1.5.1, so that we can follow up by deprecating now outdated packages without warnings.

Bumps in the docs app from 1.19.2 to 1.19.4 to fix safari logo bug