Update react monorepo (major) - #82
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 22, 2020 13:11
12af71b to
294ebd7
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
April 26, 2021 13:26
294ebd7 to
227f61d
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
May 7, 2021 09:54
227f61d to
5d3fe59
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
May 14, 2021 10:45
5d3fe59 to
eb49ad7
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
April 25, 2022 01:45
eb49ad7 to
46133d9
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
May 15, 2022 23:38
46133d9 to
d7a9199
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
June 18, 2022 16:49
d7a9199 to
8961617
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
September 25, 2022 16:39
8961617 to
f472bb5
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
November 20, 2022 12:37
f472bb5 to
adfc9a0
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
April 26, 2024 19:19
32e0435 to
89a6341
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 11, 2024 15:14
89a6341 to
3b4608c
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
December 5, 2024 18:48
3b4608c to
4803429
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
February 28, 2025 19:48
4803429 to
7f01fd1
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
March 28, 2025 21:43
7f01fd1 to
c2066a8
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
April 21, 2025 22:46
15e82a4 to
2f24dcd
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
July 28, 2025 18:09
2f24dcd to
03b4f38
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
October 4, 2025 01:50
2f37c5b to
72a4fa3
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 9, 2025 01:01
72a4fa3 to
69de853
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
October 25, 2025 00:10
27f7027 to
1811c6b
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
November 10, 2025 14:14
1811c6b to
35389d6
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
November 18, 2025 14:57
35389d6 to
bf839fc
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
December 3, 2025 19:56
bf839fc to
798d8bf
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
December 12, 2025 04:07
0ea9b81 to
327fd55
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
January 8, 2026 18:44
15a1858 to
d47982a
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
January 23, 2026 18:09
d7b1e04 to
80444c6
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
February 2, 2026 21:55
e48ded7 to
b8f2840
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
February 17, 2026 22:02
bbb500f to
566219e
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
March 5, 2026 15:58
566219e to
4383500
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
March 13, 2026 11:16
4383500 to
d5b9149
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
April 1, 2026 21:16
55b4f80 to
e7a950f
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
April 8, 2026 19:38
e7a950f to
0f68e45
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
April 17, 2026 21:14
8375135 to
936c808
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
April 29, 2026 11:34
936c808 to
2dbaf19
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
May 12, 2026 11:57
2a1f554 to
4c4c597
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
May 18, 2026 16:04
4c4c597 to
49d17f1
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
June 1, 2026 20:56
0e95583 to
09ca3af
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
June 11, 2026 17:16
09ca3af to
9570d34
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
July 17, 2026 01:31
3032f50 to
872788f
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
July 21, 2026 17:02
6c048e4 to
5e1a4fe
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
July 24, 2026 18:16
5e1a4fe to
ed0415b
Compare
renovate
Bot
force-pushed
the
renovate/major-react-monorepo
branch
from
July 30, 2026 20:05
ed0415b to
2f6e63c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.1.0→7.1.1^16.13.1→^16.13.1 || ^19.0.016.13.1→19.2.8^16.13.1→^16.13.1 || ^19.0.016.13.1→19.2.8Release Notes
facebook/react (eslint-plugin-react-hooks)
v7.1.1Compare Source
Note: 7.1.0 accidentally removed the
component-hook-factoriesrule, causing errors for users who referenced it in their ESLint config. This is now fixed.component-hook-factoriesrule for backwards compatibility. (@mofeiZ in #36307)v7.1.0Compare Source
This release adds ESLint v10 support, improves performance by skipping compilation for non-React files, and includes compiler lint improvements including better
set-state-in-effectdetection, improved ref validation, and more helpful error reporting.useEffectEventchecks in component syntax. (@jbrown215 in #35041)set-state-in-effectvalidation with fewer false negatives. (@jorge-cab in #35134, @josephsavona in #35147, @jackpope in #35214, @chesnokov-tony in #35419, @jsleitor in #36107)v7.0.1Compare Source
useEffectEventvalues as JSX props to guard against accidental propagation. (#34820 by @jf-eirinha)export =so eslint-plugin-react-hooks emits correct types for consumers in Node16 ESM projects. (#34949 by @karlhorky)configs.flatso theconfigsexport is always defined. (#34950 by @poteto)v7.0.0Compare Source
This release slims down presets to just 2 configurations (
recommendedandrecommended-latest), and all compiler rules are enabled by default.recommended-latest-legacyandflat/recommendedconfigs. The plugin now providesrecommended(legacy and flat configs with all recommended rules), andrecommended-latest(legacy and flat configs with all recommended rules plus new bleeding edge experimental compiler rules). (@poteto in #34757)v6.1.1Compare Source
Note: 6.1.0 accidentally allowed use of
recommendedwithout flat config, causing errors when used with ESLint v9'sdefineConfig()helper. This has been fixed in 6.1.1.recommendedconfig for flat config compatibility. Therecommendedconfig has been converted to flat config format. Non-flat config users should userecommended-legacyinstead. (@poteto in #34700)recommended-latestandrecommended-latest-legacyconfigs that include React Compiler rules. (@poteto in #34675)NoUnusedOptOutDirectivesrule. (@poteto in #34703)hermes-parserand dependency. (@poteto in #34719)@babel/plugin-proposal-private-methodsdependency. (@ArnaudBarre and @josephsavona in #34715)v6.1.0Compare Source
Note: Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.
recommendedpreset. Legacy config moved torecommended-legacy. (@michaelfaith in #32457)usewithin try/catch blocks. (@poteto in #34040)useEffectEventfunctions in arbitrary closures. (@jbrown215 in #33544)React.useEffectin addition touseEffectin rules-of-hooks. (@Ayc0 in #34076)react-hookssettings config option that to acceptadditionalEffectHooksthat are used across exhaustive-deps and rules-of-hooks rules. (@jbrown215) in #34497v6.0.0Compare Source
Accidentally released. See 6.1.0 for the actual changes.
v5.2.0Compare Source
do/whileloops (@tyxla in #31720)v5.1.0Compare Source
do/whileloops (@tyxla in #28714)asexpression (@mskelton in #31119)v5.0.0Compare Source
_Buttonor_componentare no longer valid. (@kassens) in #25162useActionStatestable. (@eps1lon in #29665)asexpression in callback. (@StyleShit in #28202)asexpressions in deps array. (@StyleShit in #28189)React.use()the same asuse(). (@kassens in #27769)use()lint to non-experimental. (@kassens in #27768)asexpressions. (@cpojer in #27590)useEffect(fn, undefined). (@kassens in #27525)useEventtouseEffectEvent. (@sebmarkbage in #25881)useEventfunctions in dependency lists. (@poteto in #25512)useEventreferences instead. (@poteto in #25319)RulesOfHookswithuseEventrules. (@poteto in #25285)v4.6.2Compare Source
v4.6.1Compare Source
v4.6.0v4.5.0v4.4.0v4.3.0useTransitionsignature in the rule. (@rickhanlonii in #20976)v4.2.0v4.1.2v4.1.1react/react (react)
v19.2.8Compare Source
v19.2.7Compare Source
React Server Components
FormDataentries in Server Actions which regressed in 19.2.6 (@unstubbable #36566)v19.2.6Compare Source
React Server Components
v19.2.5Compare Source
React Server Components
v19.2.4Compare Source
React Server Components
v19.2.3Compare Source
React Server Components
v19.2.2Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon #35290)v19.2.1Compare Source
React Server Components
v19.2.0Compare Source
Below is a list of all new features, APIs, and bug fixes.
Read the React 19.2 release post for more information.
New React Features
<Activity>: A new API to hide and restore the UI and internal state of its children.useEffectEventis a React Hook that lets you extract non-reactive logic into an Effect Event.cacheSignal(for RSCs) lets your know when thecache()lifetime is over.New React DOM Features
resume: to resume a prerender to a stream.resumeAndPrerender: to resume a prerender to HTML.resumeToPipeableStream: to resume a prerender to a stream.resumeAndPrerenderToNodeStream: to resume a prerender to HTML.prerenderAPIs to return apostponedstate that can be passed to theresumeAPIs.Notable changes
<ViewTransition>Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.prerender,renderToReadableStream) to server-side-rendering APIs for Node.js:IDs generated by useIdAll Changes
React
<Activity />was developed over many years, starting beforeClassComponent.setState(@acdlite @sebmarkbage and many others)%oplaceholder (@eps1lon #34198)useDeferredValueloop in popstate event (@acdlite #32821)useDeferredValue(@acdlite #34376)cacheSignal(@sebmarkbage #33557)React DOM
:for IDs generated byuseId(@sebmarkbage, @eps1lon: #32001, facebook#33342#33099, #33422)nonceto be used on hoistable styles (@Andarist #32461)React.useinsideReact.lazy-ed Component (@hi-ogawa #33941)progressiveChunkSizeoption for server-side-rendering APIs (@sebmarkbage #33027)React Server Components
<img>and<link>using hints before they're rendered (@sebmarkbage #34604)filterStackFrame(@eps1lon #33707)React Reconciler
on*handlers to account for upcoming experimental APIsv19.1.9Compare Source
v19.1.8Compare Source
React Server Components
FormDataentries in Server Actions which regressed in 19.1.7 (@unstubbable #36567)v19.1.7Compare Source
React Server Components
v19.1.6Compare Source
React Server Components
v19.1.5Compare Source
React Server Components
v19.1.4Compare Source
React Server Components
v19.1.3Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon #35290)v19.1.2Compare Source
React Server Components
v19.1.1Compare Source
React
v19.1.0Compare Source
Owner Stack
An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.
#32538, #32529, #32538
React
useIdto use valid CSS selectors, changing format from:r123:to«r123». #32001React DOM
hrefattribute is an empty string #31783getHoistableRoot()didn’t work properly when the container was a Document #32321<!-- -->) as a DOM container. #32250<script>and<template>tags to be nested within<select>tags. #31837use-sync-external-store
exportsfield topackage.jsonforuse-sync-external-storeto support various entrypoints. #25231React Server Components
unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724registerServerReferencein client builds to handle server references in different environments. #32534v19.0.8Compare Source
v19.0.7Compare Source
React Server Components
FormDataentries in Server Actions which regressed in 19.0.6 (@unstubbable #36568)v19.0.6Compare Source
React Server Components
v19.0.5Compare Source
React Server Components
v19.0.4Compare Source
React Server Components
v19.0.3Compare Source
React Server Components
v19.0.2Compare Source
React Server Components
v19.0.1Compare Source
React Server Components
v19.0.0Compare Source
Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.
New Features
React
startTransitioncan now accept async functions. Functions passed tostartTransitionare called “Actions”. A given Transition can include one or more Actions which update state in the background and update the UI with one commit. In addition to updating state, Actions can now perform side effects including async requests, and the Action will wait for the work to finish before finishing the Transition. This feature allows Transitions to include side effects likefetch()in the pending state, and provides support for error handling, and optimistic updates.useActionState: is a new hook to order Actions inside of a Transition with access to the state of the action, and the pending state. It accepts a reducer that can call Actions, and the initial state used for first render. It also accepts an optional string that is used if the action is passed to a formactionprop to support progressive enhancement in forms.useOptimistic: is a new hook to update state while a Transition is in progress. It returns the state, and a set function that can be called inside a transition to “optimistically” update the state to expected final value immediately while the Transition completes in the background. When the transition finishes, the state is updated to the new value.use: is a new API that allows reading resources in render. In React 19,useaccepts a promise or Context. If provided a promise,usewill suspend until a value is resolved.usecan only be used in render but can be called conditionally.refas a prop: Refs can now be used as props, removing the need forforwardRef.React DOM Client
<form> actionprop: Form Actions allow you to manage forms automatically and integrate withuseFormStatus. When a<form> actionsucceeds, React will automatically reset the form for uncontrolled components. The form can be reset manually with the newrequestFormResetAPI.<button> and <input> formActionprop: Actions can be passed to theformActionprop to configure form submission behavior. This allows using different Actions depending on the input.useFormStatus: is a new hook that provides the status of the parent<form> action, as if the form was a Context provider. The hook returns the values:pending,data,method, andaction.<head>section of the document.<head>on the client before revealing the content of a Suspense boundary that depends on that stylesheet.preinit,preload,prefetchDNS, andpreconnectAPIs to optimize initial page loads by moving discovery of additional resources like fonts out of stylesheet loading. They can also be used to prefetch resources used by an anticipated navigation.React DOM Server
prerenderandprerenderToNodeStreamAPIs for static site generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. UnlikerenderToString, they wait for data to load for HTML generation.React Server Components
Deprecations
element.refaccess: React 19 supports ref as a prop, so we’re deprecatingelement.refin favor ofelement.props.ref. Accessing will result in a warning.react-test-renderer: In React 19, react-test-renderer logs a deprecation warning and has switched to concurrent rendering for web usage. We recommend migrating your tests to @testing-library/react or @testing-library/react-nativeBreaking Changes
React 19 brings in a number of breaking changes, including the removals of long-deprecated APIs. We recommend first upgrading to
18.3.1, where we've added additional deprecation warnings. Check out the upgrade guide for more details and guidance on codemodding.React
onUncaughtErrorandonCaughtErrormethods tocreateRootandhydrateRootto customize this error handling.propTypes: UsingpropTypeswill now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.defaultPropsfor functions: ES6 default parameters can be used in place. Class components continue to supportdefaultPropssince there is no ES6 alternative.contextTypesandgetChildContext: Legacy Context for class components has been removed in favor of thecontextTypeAPI.React.createFactory: Now that JSX is broadly supported, allcreateFactoryusage can be migrated to JSX components.react-test-renderer/shallow: This has been a re-export of react-shallow-renderer since React 18. If needed, you can continue to use the third-party package directly. We recommend using @testing-library/react or @testing-library/react-native instead.React DOM
react-dom/test-utils: We’ve movedactfromreact-dom/test-utilsto react. All other utilities have been removed.ReactDOM.render,ReactDOM.hydrate: These have been removed in favor of the concurrent equivalents:ReactDOM.createRootandReactDOM.hydrateRoot.unmountComponentAtNode: Removed in favor ofroot.unmount().ReactDOM.findDOMNode: You can replaceReactDOM.findDOMNodewith DOM Refs.Notable Changes
React
<Context>as a provider: You can now render<Context>as a provider instead of<Context.Provider>.useDeferredValueinitial value argument: When provided,useDeferredValuewill return the initial value for the initial render of a component, then schedule a re-render in the background with thedeferredValuereturned.useMemoanduseCallbackwill now reuse the memoized results from the first render, during the second render. Additionally, StrictMode will now double-invoke ref callback functions on initial mount.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.