Five dated news digests and five engineering Q&A entries. Each item cites primary documentation or release artifacts (not generic placeholders).
The React team published React 19.0.0 with async-capable Actions, useActionState, useOptimistic, and the use API for promise/context consumption.
Form integrations include native action props plus useFormStatus for pending UI.
Patch release 19.1.0 highlights development-time owner stacks (captureOwnerStack) and refines Suspense scheduling across client and server renderers.
Teams upgrading from 19.0 should skim the changelog for hydration-related fixes.
The official upgrade guide explains how to remove deprecated patterns (string refs, legacy context, etc.) ahead of enabling React 19 in production bundles.
Use Strict Mode double-rendering locally to flush unsafe side effects.
The monorepo changelog is the low-level companion to marketing blog posts: it enumerates package-level fixes for react-dom, flight, and experimental flags.
Pin exact versions during regression hunts instead of floating ^19 ranges.
The React docs describe how startTransition keeps UI responsive while async Actions resolve—important when mixing optimistic UI with server validation.
Pair reading with the new hooks API reference entries shipped alongside 19.
React 19 allows refs to be passed as ordinary props to function components, reducing the need for forwardRef in many cases.
Audit library code you own before deleting wrappers—third-party types may lag.
Use Actions with useTransition or useActionState so pending, error, and success states stay declarative instead of scattering manual booleans.
Server Actions require framework support—follow your meta-framework docs when deploying on the edge.
Release notes for 19.1 call out a formatting change in generated IDs; snapshot tests that hard-coded colon-based tokens may need updates.
Prefer asserting structure (prefix + uniqueness) rather than exact strings.
The upgrade guide enumerates deprecated APIs that Strict Mode surfaces; fix warnings on React 18 before jumping to 19 to avoid combined noise.
Record a component inventory so legacy class lifecycles are not missed.
Use the changelog’s package sections to identify which workspace (react, react-dom, scheduler) changed, then binary-search tags on GitHub.
Reproduce with a minimal CodeSandbox linked to an issue if you need maintainer help.