From bf0c0268b5738594591bd24500351bf82b1fd9d0 Mon Sep 17 00:00:00 2001 From: sebastien Date: Fri, 10 May 2024 14:56:17 +0200 Subject: [PATCH] fix v3.3 blog post --- website/blog/releases/3.3/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/releases/3.3/index.mdx b/website/blog/releases/3.3/index.mdx index d4858687ef95..88907a9d90fd 100644 --- a/website/blog/releases/3.3/index.mdx +++ b/website/blog/releases/3.3/index.mdx @@ -21,7 +21,7 @@ import IframeWindow from '@site/src/components/BrowserWindow/IframeWindow'; ### Prepare for React 19 -The React core team recently [released the first **React 19 beta**](https://react.dev/blog/2024/04/25/react-19). They also [published an upgrade guide and a ** React v18.3 release**](https://react.dev/blog/2024/04/25/react-19-upgrade-guide) with new warnings to help us identify issues **before upgrading to React 19**. +The React core team recently [released the first **React 19 beta**](https://react.dev/blog/2024/04/25/react-19). They also [published an upgrade guide and a **React v18.3 release**](https://react.dev/blog/2024/04/25/react-19-upgrade-guide) with new warnings to help us identify issues **before upgrading to React 19**. Docusaurus v3 depends on React `18.x`. When initializing a new Docusaurus sites, it will use that new React `18.3` release. It's also the case if you decide to upgrade your dependencies, or re-generate your package manager lockfile.