React Daily: Release Pipeline Overhaul and Critical Bug Fixes
The React team merged four significant pull requests today, headlined by a major consolidation of the release process that removes five separate workflows in favor of a single unified system. A critical bug fix addresses crashes in server-side rendering when Flight chunks are rejected.
Duration: PT1M48S
Transcript
Good morning, this is React Daily for May 26th, 2026.
Sebastian Silbermann merged a unified release process that consolidates nightlies and stable releases into a single workflow. The change removes five separate release workflows and adds enhanced security requirements - all releases now require two-person review with no self-approval allowed. This represents a significant shift as all future releases will be handled entirely through continuous integration.
Janka Uryga merged a critical fix for Fizz server-side rendering that was causing crashes when capturing call sites of stalled use() calls. The issue occurred when Flight chunks were rejected between abort and stack capture, putting ReactPromise into an invalid state. The fix ensures rejected thenables receive the same patching treatment as fulfilled ones.
Silbermann also merged CI improvements removing redundant node_modules caches across ten workflow files. The team identified that actions/cache and actions/setup-node were creating equivalent cache keys, making one redundant. This optimization should improve build times across the development pipeline.
Finally, the team stopped transpiling computed property names, dropping support that's been available in browsers and Node.js for ten years. This change only affects react-server-dom packages in development and normalizes code between development and production builds.
What's next: The team is considering a more modern target matrix for React 20, and the new unified release process should streamline future deployments while improving security oversight.
That's your React Daily briefing. I'm your host, we'll see you tomorrow.