Next.js: להתכונן לעדכון האבטחה של 3 בנובמבר בלי לנחש גרסאות

Read this news or bug-fix article as reference material:
https://nethanelfitoussi.com/article/nextjs-november-3-security-release-preparation?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Additional project setup instructions:
Prepare a Next.js patch-readiness report from https://nextjs.org/blog/upcoming-nextjs-security-release-november-2026 . This notice was reviewed on 28 October 2026 and schedules seven medium-severity fixes for 3 November 2026. It does not yet publish affected ranges, full impact, CVEs or fixed release numbers. Recheck the current official notice before deciding what is now available. Inventory locked and deployed next/react/react-dom versions and the package manager. Identify staging tests, owners and rollback steps. Apply already available October fixes through a separately reviewed compatible change; do not postpone them for November. Do not invent a future version, downgrade protections, change production or schedule an automation without my request.

Check the dated advisory and current official vendor guidance. Identify whether my installed version and configuration are affected before proposing a fix.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.