[v13] chore: increase required React et al. versions

Author: mdjastrzebski

package.json

@@ -57,9 +57,9 @@
   },
   "peerDependencies": {
     "jest": ">=28.0.0",
-    "react": ">=18.2.0",
-    "react-native": ">=0.73",
-    "react-test-renderer": ">=18.2.0"
+    "react": ">=18.3.0",
+    "react-native": ">=0.75",
+    "react-test-renderer": ">=18.3.0"
   },
   "peerDependenciesMeta": {
     "jest": {

website/docs/12.x/docs/api/misc/async.mdx

@@ -53,12 +53,6 @@ Avoiding side effects in `expectation` callback can be partially enforced with t
 
 It is also recommended to have a [single assertion per each `waitFor`](https://kentcdodds.com/blog/common-mistakes-with-react-testing-library#having-multiple-assertions-in-a-single-waitfor-callback) for more consistency and faster failing tests. If you want to make several assertions, then they should be in seperate `waitFor` calls. In many cases you won't actually need to wrap the second assertion in `waitFor` since the first one will do the waiting required for asynchronous change to happen.
 
-### Using a React Native version < 0.71 with Jest fake timers
-
-:::caution
-When using a version of React Native < 0.71 and modern fake timers (the default for `Jest` >= 27), `waitFor` won't work (it will always timeout even if `expectation()` doesn't throw) unless you use the custom [@testing-library/react-native preset](https://github.com/callstack/react-native-testing-library#custom-jest-preset).
-:::
-
 `waitFor` checks whether Jest fake timers are enabled and adapts its behavior in such case. The following snippet is a simplified version of how it behaves when fake timers are enabled:
 
 ```tsx
@@ -96,10 +90,6 @@ await waitFor(() => {
 }, 10000);
 ```
 
-:::info
-In order to properly use `waitFor` you need at least React >=16.9.0 (featuring async `act`) or React Native >=0.61 (which comes with React >=16.9.0).
-:::
-
 :::note
 If you receive warnings related to `act()` function consult our [Undestanding Act](docs/advanced/understanding-act.md) function document.
 :::
@@ -129,10 +119,6 @@ This method expects that the element is initially present in the render tree and
 
 You can use any of `getBy`, `getAllBy`, `queryBy` and `queryAllBy` queries for `expectation` parameter.
 
-:::info
-In order to properly use `waitForElementToBeRemoved` you need at least React >=16.9.0 (featuring async `act`) or React Native >=0.61 (which comes with React >=16.9.0).
-:::
-
 :::note
 If you receive warnings related to `act()` function consult our [Undestanding Act](docs/advanced/understanding-act.md) function document.
 :::

website/docs/MigrationV13.md renamed to website/docs/12.x/docs/migration/v13.mdx

@@ -1,14 +1,7 @@
-id: migration-v13
-title: Migration to 13.0
-
----
-
-import TOCInline from '@theme/TOCInline';
+# Migration to 13.0
 
 Migration to React Native Testing Library version 13 from version 12.x.
 
-<TOCInline toc={toc} />
-
 # Breaking changes
 
 ## Supported React and React Native versions
@@ -23,11 +16,11 @@ This deprecated query has been removed as is typically too general to give meani
 
 - [`*ByRole`](#by-role) query with relevant state options: `disabled`, `selected`, `checked`, `expanded` and `busy`
 - use built-in Jest matchers to check the state of element found using some other query:
-  - enabled state: [`toBeEnabled()` / `toBeDisabled()`](jest-matchers#tobeenabled)
-  - checked state: [`toBeChecked()` / `toBePartiallyChecked()`](jest-matchers#tobechecked)
-  - selected state: [`toBeSelected()`](jest-matchers#tobeselected)
-  - expanded state: [`toBeExpanded()` / `toBeCollapsed()`](jest-matchers#tobeexpanded)
-  - busy state: [`toBeBusy()`](jest-matchers#tobebusy)
+  - enabled state: [`toBeEnabled()` / `toBeDisabled()`](docs/api/jest-matchers#tobeenabled)
+  - checked state: [`toBeChecked()` / `toBePartiallyChecked()`](docs/api/jest-matchers#tobechecked)
+  - selected state: [`toBeSelected()`](docs/api/jest-matchers#tobeselected)
+  - expanded state: [`toBeExpanded()` / `toBeCollapsed()`](docs/api/jest-matchers#tobeexpanded)
+  - busy state: [`toBeBusy()`](docs/api/jest-matchers#tobebusy)
 
 ```ts
 // Replace this
@@ -45,7 +38,7 @@ expect(view).toBeDisabled(); // Assert its accessibility state
 
 This deprecated query has been removed as is typically too general to give meaningful results. Use one of the following options:
 
-- [`toHaveAccessibilityValue()`](jest-matchers#tohaveaccessibilityvalue) Jest matcher to check the state of element found using some other query
+- [`toHaveAccessibilityValue()`](docs/api/jest-matchers#tohaveaccessibilityvalue) Jest matcher to check the state of element found using some other query
 - [`*ByRole`](#by-role) query with `value` option
 
 ```ts
@@ -62,7 +55,7 @@ expect(view).toHaveAccessibilityValue({ now: 50, min: 0, max: 50 }); // Assert i
 
 ## Removed `debug.shallow`
 
-For a time being we didn't support shallow rendering. Now we are removing the last remains of it: `debug.shallow()`. If you are interested in shallow rendering see [here](migration-v2#removed-global-shallow-function).
+For a time being we didn't support shallow rendering. Now we are removing the last remains of it: `debug.shallow()`. If you are interested in shallow rendering see [here](docs/migration/previous/v2#removed-global-shallow-function).
 
 # Other changes
 
@@ -72,4 +65,4 @@ This should not break any tests.
 
 ## Full Changelog
 
-https://github.com/callstack/react-native-testing-library/compare/v12.5.0...v13.0.0
+https://github.com/callstack/react-native-testing-library/compare/v12.5.2...v13.0.0

yarn.lock

@@ -2931,9 +2931,9 @@ __metadata:
     typescript: "npm:^5.5.4"
   peerDependencies:
     jest: ">=28.0.0"
-    react: ">=18.2.0"
-    react-native: ">=0.73"
-    react-test-renderer: ">=18.2.0"
+    react: ">=18.3.0"
+    react-native: ">=0.75"
+    react-test-renderer: ">=18.3.0"
   peerDependenciesMeta:
     jest:
       optional: true