diff --git a/DateRangeInput.md b/DateRangeInput.md
index 354ab924cc0..3e17687dc1a 100644
--- a/DateRangeInput.md
+++ b/DateRangeInput.md
@@ -9,14 +9,20 @@ This [Enterprise Edition](https://react-admin-ee.marmelab.com)<img class="icon"
 
 ![DateRangeInput](./img/DateRangeInput.png)
 
-**Note**: `<DateRangeInput>` is a wrapper around the [Material UI X Date Range Picker](https://mui.com/x/react-date-pickers/date-range-picker/), which is a MUI X Pro package. This means that you need to own a [MUI X Pro license](https://mui.com/x/introduction/licensing/#pro-plan) to use it.
+**Note**: `<DateRangeInput>` is a wrapper around the [Material UI X Date Range Picker](https://mui.com/x/react-date-pickers/date-range-picker/), which is a MUI X Pro package. This means that you need to own a [MUI X Pro license](https://mui.com/x/introduction/licensing/#pro-plan) to use it and install the package:
+
+```sh
+npm install --save @mui/x-date-pickers-pro
+# or
+yarn add @mui/x-date-pickers-pro
+```
 
 ## Usage
 
 Use `<DateRangeInput>` inside a form component (`<SimpleForm>`, `<TabbedForm>`, `<LongForm>`, etc.) to allow users to pick a start and an end date.
 
 ```tsx
-import { DateRangeInput } from '@react-admin/ra-form-layout';
+import { DateRangeInput } from '@react-admin/ra-form-layout/DateRangeInput';
 import { Edit, SimpleForm } from 'react-admin';
 
 export const EventEdit = () => (
@@ -106,7 +112,7 @@ import {
     SimpleForm,
     TextInput,
 } from "react-admin";
-import { DateRangeInput } from '@react-admin/ra-form-layout';
+import { DateRangeInput } from '@react-admin/ra-form-layout/DateRangeInput';
 
 const requiredValues = dates =>
     !dates || isEmpty(dates[0]) || isEmpty(dates[1])
diff --git a/ReferenceManyToManyField.md b/ReferenceManyToManyField.md
index 87c7ada4fbc..daabd6b2bae 100644
--- a/ReferenceManyToManyField.md
+++ b/ReferenceManyToManyField.md
@@ -5,7 +5,7 @@ title: "The ReferenceManyToManyField Component"
 
 # `<ReferenceManyToManyField>`
 
-This [Enterprise Edition](https://react-admin-ee.marmelab.com)<img class="icon" src="./img/premium.svg" /> component fetches a list of referenced records by lookup in an associative table, and passes the records down to its child component, which must be an iterator component (e.g. `<SingleFieldList>`).
+This [Enterprise Edition](https://react-admin-ee.marmelab.com)<img class="icon" src="./img/premium.svg" alt="React Admin Enterprise Edition icon" /> component fetches a list of referenced records by lookup in an associative table, and passes the records down to its child component, which must be an iterator component (e.g. `<SingleFieldList>`).
 
 !["ReferenceManyToManyField example showing band's venues"](./img/reference-many-to-many-field.png)
 
@@ -15,7 +15,7 @@ Note: The `<ReferenceManyToManyField>` cannot currently display multiple records
 
 Let's imagine that you're writing an app managing concerts for artists. The data model features a many-to-many relationship between the `bands` and `venues` tables through a `performances` associative table.
 
-```
+```txt
 ┌─────────┐       ┌──────────────┐      ┌───────────────┐
 │ bands   │       │ performances │      │ venues        │
 │---------│       │--------------│      │---------------│
@@ -28,7 +28,7 @@ Let's imagine that you're writing an app managing concerts for artists. The data
 
 In this example, `bands.id` matches `performances.band_id`, and `performances.venue_id` matches `venues.id`.
 
-To allow users see the `venues` for a given `band` in `<SingleFieldList>`, wrap that component in `<ReferenceManyToManyField>` where you define the relationship via the `reference`, `through` and `using` props: 
+To allow users see the `venues` for a given `band` in `<SingleFieldList>`, wrap that component in `<ReferenceManyToManyField>` where you define the relationship via the `reference`, `through` and `using` props:
 
 ```tsx
 import React from 'react';
@@ -61,17 +61,18 @@ export const BandShow = () => (
 | ----------- | -------- | ------------------------------------------- | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `children`  | Required | `element`                                   | -                                | An iterator element (e.g. `<SingleFieldList>` or `<Datagrid>`). The iterator element usually has one or more child `<Field>` components.                                                                          |
 | `reference` | Required | `string`                                    | -                                | Name of the reference resource, e.g. 'venues'                                                                                                                                                                    |
-| `through`   | Required | `string`                                    | -                                | Name of the resource for the associative table, e.g. 'performances'                                                                                                                                               
+| `through`   | Required | `string`                                    | -                                | Name of the resource for the associative table, e.g. 'performances'                                                                                                                                               |
 | `filter`    | Optional | `object`                                    | `{}`                             | Filter for the associative table (passed to the `getManyReference()` call)                                                                                                                                        |
 | `joinLimit` | Optional | `number`                                    | 100                              | Limit for the number of results fetched from the associative table. Should be **greater than `perPage`**                                                                                                          |
 | `perPage`   | Optional | `number`                                    | 25                               | Limit the number of displayed result after  `getManyReference` is called. Useful when using a pagination component. Should be **smaller than `joinLimit`**                                                        |
+| `queryOptions` | Optional | `UseQueryOptions`                        | -                                | Query options for the `getMany` and `getManyReference` calls                                                                                                                            |
 | `sort`      | Optional | `{ field: string, order: 'ASC' or 'DESC' }` | `{ field: 'id', order: 'DESC' }` | Sort for the associative table (passed to the `getManyReference()` call)                                                                                                                                          |
 | `source`    | Optional | `string`                                    | `'id'`                           | Name of the field containing the identity of the main resource. Used determine the value to look for in the associative table.                                                                                    |
 | `using`     | Optional | `string`                                    | `'[resource]_id,[reference]_id'` | Tuple (comma separated) of the two field names used as foreign keys, e.g 'band_id,venue_id'. The tuple should start with the field pointing to the resource, and finish with the field pointing to the reference |
 
 ## `children`
 
-`<ReferenceManyToManyField>` expects an _iterator_ component as child, i.e. a component working inside a `ListContext`. 
+`<ReferenceManyToManyField>` expects an _iterator_ component as child, i.e. a component working inside a `ListContext`.
 
 This means you can use a `<Datagrid>` instead of a `<SingleFieldList>`, which is useful if you want to display more details about related records. For instance, to display the venue `name` and `location`:
 
@@ -105,6 +106,7 @@ export const BandShow = () => (
 You can filter the records of the associative table (e.g. `performances`) using the `filter` prop. This `filter` is passed to the `getManyReference()` call.
 
 {% raw %}
+
 ```tsx
 <ReferenceManyToManyField
     reference="venues"
@@ -115,6 +117,7 @@ You can filter the records of the associative table (e.g. `performances`) using
     {/* ... */}
 </ReferenceManyToManyField>
 ```
+
 {% endraw %}
 
 ## `joinLimit`
@@ -165,6 +168,27 @@ import { Pagination } from 'react-admin';
 </ReferenceManyToManyField>
 ```
 
+## `queryOptions`
+
+Use the `queryOptions` prop to customize the queries for `getMany` and `getManyReference`.
+
+You can for instance use it to pass [a custom meta](./Actions.md#meta-parameter) to the dataProvider.
+
+{% raw %}
+
+```tsx
+<ReferenceManyToManyField
+    reference="venues"
+    through="performances"
+    using="band_id,venue_id"
+    queryOptions={{ meta: { myParameter: 'value' } }}
+>
+    {/* ... */}
+</ReferenceManyToManyField>
+```
+
+{% endraw %}
+
 ## `reference`
 
 The name of the target resource to fetch.
@@ -187,6 +211,7 @@ For instance, if you want to display the `venues` of a given `bands`, through `p
 By default, react-admin orders the possible values by `id` desc for the associative table (e.g. `performances`). You can change this order by setting the `sort` prop (an object with `field` and `order` properties) to be applied to the associative resource.
 
 {% raw %}
+
 ```tsx
 <ReferenceManyToManyField
     reference="venues"
@@ -197,6 +222,7 @@ By default, react-admin orders the possible values by `id` desc for the associat
     {/* ... */}
 </ReferenceManyToManyField>
 ```
+
 {% endraw %}
 
 ## `source`
@@ -242,8 +268,8 @@ You can specify the columns to use in the associative `using` the using prop.
 
 `<ReferenceManyToManyField>` fetches the `dataProvider` twice in a row:
 
--   once to get the records of the associative resource (`performances` in this case), using a `getManyReference()` call
--   once to get the records of the reference resource (`venues` in this case), using a `getMany()` call.
+- once to get the records of the associative resource (`performances` in this case), using a `getManyReference()` call
+- once to get the records of the reference resource (`venues` in this case), using a `getMany()` call.
 
 For instance, if the user displays the band of id `123`, `<ReferenceManyToManyField>` first issues the following query to the `dataProvider`:
 
@@ -286,4 +312,4 @@ And receives the reference venues:
     ],
     "total": 3
 }
-```
\ No newline at end of file
+```
diff --git a/ReferenceManyToManyInput.md b/ReferenceManyToManyInput.md
index bb1a571404d..76ef74a105f 100644
--- a/ReferenceManyToManyInput.md
+++ b/ReferenceManyToManyInput.md
@@ -5,7 +5,7 @@ title: "The ReferenceManyToManyInput Component"
 
 # `<ReferenceManyToManyInput>`
 
-This [Enterprise Edition](https://react-admin-ee.marmelab.com)<img class="icon" src="./img/premium.svg" /> component allows to create, edit or remove relationships between two resources sharing an associative table. The changes in the associative table are sent to the dataProvider _when the user submits the form_, so that they can cancel the changes before submission.
+This [Enterprise Edition](https://react-admin-ee.marmelab.com)<img class="icon" src="./img/premium.svg" alt="React Admin Enterprise Edition icon" /> component allows to create, edit or remove relationships between two resources sharing an associative table. The changes in the associative table are sent to the dataProvider _when the user submits the form_, so that they can cancel the changes before submission.
 
 <video controls autoplay playsinline muted loop width="100%">
   <source src="https://react-admin-ee.marmelab.com/assets/reference-many-to-many-input.mp4" type="video/mp4" />
@@ -18,7 +18,7 @@ This [Enterprise Edition](https://react-admin-ee.marmelab.com)<img class="icon"
 
 Let's imagine that you're writing an app managing concerts for artists. The data model features a many-to-many relationship between the `bands` and `venues` tables through a `performances` associative table.
 
-```
+```txt
 ┌─────────┐       ┌──────────────┐      ┌───────────────┐
 │ bands   │       │ performances │      │ venues        │
 │---------│       │--------------│      │---------------│
@@ -29,7 +29,7 @@ Let's imagine that you're writing an app managing concerts for artists. The data
 └─────────┘       └──────────────┘      └───────────────┘
 ```
 
-In this example, `bands.id` matches `performances.band_id`, and `performances.venue_id` matches `venues.id`. 
+In this example, `bands.id` matches `performances.band_id`, and `performances.venue_id` matches `venues.id`.
 
 To let users edit the `venues` for given `band` in an `<AutocompleteArrayInput>`, wrap that input in a `<ReferenceManyToManyInput>` where you define the relationship via the `reference`, `through` and `using` props:
 
@@ -60,7 +60,7 @@ export const BandEdit = () => (
 
 Note that although all possible child components support a `defaultValue` prop, it will only be applied on create views.
 
-**Tip**: If you need to edit the fields of the associative table (e.g. the `date` in `performances`), you can use a [`<ReferenceManyInput>`](./ReferenceManyInput.md) instead of `<ReferenceManyToManyInput>`. 
+**Tip**: If you need to edit the fields of the associative table (e.g. the `date` in `performances`), you can use a [`<ReferenceManyInput>`](./ReferenceManyInput.md) instead of `<ReferenceManyToManyInput>`.
 
 ![Screenshot showing the use of ReferenceManyInput instead of ReferenceManyToManyInput](./img/reference-many-input-band-edit.png)
 
@@ -107,8 +107,10 @@ const BandEdit = () => (
 | `through`        | Required | `string`                                    | -                                  | Name of the resource for the associative table, e.g. 'book_authors'                                                                                                                                               |
 | `filter`         | Optional | `object`                                    | `{}`                               | Filter for the associative table (passed to the `getManyReference()` call)                                                                                                                                        |
 | `filter Choices`  | Optional | `object`                                    | `{}`                               | Filter for the possible choices fetched from the reference table (passed to the `getList()` call)                                                                                                                 |
+| `mutationOptions` | Optional | `{ meta, onError }`                         | -                                  | Mutation options for the `create` and `deleteMany` calls. Only `meta` and `onError` are supported.                                                                                                                |
 | `perPage`        | Optional | `number`                                    | 25                                 | Limit for the number of results fetched from the associative table                                                                                                                                                |
 | `perPage Choices` | Optional | `number`                                    | 25                                 | Limit for the number of possible choices fetched from the reference table                                                                                                                                         |
+| `queryOptions`   | Optional | `UseQueryOptions`                           | -                                  | Query options for the `getList`, `getMany` and `getManyReference` calls                                                                                                                                           |
 | `sort`           | Optional | `{ field: string, order: 'ASC' or 'DESC' }` | `{ field: 'id', order: 'DESC' }`   | Sort for the associative table (passed to the `getManyReference()` call)                                                                                                                                          |
 | `sort Choices`    | Optional | `{ field: string, order: 'ASC' or 'DESC' }` | `{ field: 'id', order: 'DESC' }`   | Sort for the possible choices fetched from the reference table (passed to the `getList()` call)                                                                                                                   |
 | `source`         | Optional | `string`                                    | `'id'`                             | Name of the field containing the identity of the main resource. Used determine the value to look for in the associative table.                                                                                    |
@@ -116,7 +118,7 @@ const BandEdit = () => (
 
 ## `children`
 
-`<ReferenceManyToManyInput>` expects a _select_ component as child, i.e. a component working inside a `ChoiceContext`. That means you can use a [`<SelectArrayInput>`](./SelectArrayInput.md), or a [`<AutocompleteArrayInput>`](./AutocompleteArrayInput.md). 
+`<ReferenceManyToManyInput>` expects a _select_ component as child, i.e. a component working inside a `ChoiceContext`. That means you can use a [`<SelectArrayInput>`](./SelectArrayInput.md), or a [`<AutocompleteArrayInput>`](./AutocompleteArrayInput.md).
 
 For instance, to allow user to choose `performances` using a `<SelectArrayInput>` instead of an `<AutocompleteArrayInput>`, you can write:
 
@@ -152,6 +154,7 @@ export const BandEdit = () => (
 You can filter the records of the associative table (e.g. `performances`) using the `filter` prop. This `filter` is passed to the `getManyReference()` call.
 
 {% raw %}
+
 ```tsx
 <ReferenceManyToManyInput
     reference="venues"
@@ -162,6 +165,7 @@ You can filter the records of the associative table (e.g. `performances`) using
     {/* ... */}
 </ReferenceManyToManyInput>
 ```
+
 {% endraw %}
 
 ## `filterChoices`
@@ -171,6 +175,7 @@ You can filter the records of the associative table (e.g. `performances`) using
 You can filter the possible values of the reference table using the `filterChoices` prop. This `filterChoices` is passed to the `getList()` call.
 
 {% raw %}
+
 ```tsx
 <ReferenceManyToManyInput
     reference="venues"
@@ -181,6 +186,28 @@ You can filter the possible values of the reference table using the `filterChoic
     {/* ... */}
 </ReferenceManyToManyInput>
 ```
+
+{% endraw %}
+
+## `mutationOptions`
+
+Use the `mutationOptions` prop to customize the `create` and `deleteMany` mutations.
+
+You can for instance use it to pass [a custom meta](./Actions.md#meta-parameter) to the dataProvider.
+
+{% raw %}
+
+```tsx
+<ReferenceManyToManyInput
+    reference="venues"
+    through="performances"
+    using="band_id,venue_id"
+    mutationOptions={{ meta: { myParameter: 'value' } }}
+>
+    {/* ... */}
+</ReferenceManyToManyInput>
+```
+
 {% endraw %}
 
 ## `perPage`
@@ -214,6 +241,28 @@ By default, react-admin displays at most 25 possible values from the reference t
     {/* ... */}
 </ReferenceManyToManyInput>
 ```
+
+## `queryOptions`
+
+Use the `queryOptions` prop to customize the queries for `getList`, `getMany` and `getManyReference`.
+
+You can for instance use it to pass [a custom meta](./Actions.md#meta-parameter) to the dataProvider.
+
+{% raw %}
+
+```tsx
+<ReferenceManyToManyInput
+    reference="venues"
+    through="performances"
+    using="band_id,venue_id"
+    queryOptions={{ meta: { myParameter: 'value' } }}
+>
+    {/* ... */}
+</ReferenceManyToManyInput>
+```
+
+{% endraw %}
+
 ## `reference`
 
 The name of the target resource to fetch.
@@ -230,11 +279,13 @@ For instance, if you want to display the venues of a given bands, through perfor
     {/* ... */}
 </ReferenceManyToManyInput>
 ```
+
 ## `sort`
 
 By default, react-admin orders the possible values by `id` desc for the associative table (e.g. `performances`). You can change this order by setting the `sort` prop (an object with `field` and `order` properties) to be applied to the associative resource.
 
 {% raw %}
+
 ```tsx
 <ReferenceManyToManyInput
     reference="venues"
@@ -245,6 +296,7 @@ By default, react-admin orders the possible values by `id` desc for the associat
     {/* ... */}
 </ReferenceManyToManyInput>
 ```
+
 {% endraw %}
 
 ## `sortChoices`
@@ -252,6 +304,7 @@ By default, react-admin orders the possible values by `id` desc for the associat
 By default, react-admin orders the possible values by `id` desc for the reference table (e.g. `venues`). You can change this order by setting the `sortChoices` prop (an object with `field` and `order` properties).
 
 {% raw %}
+
 ```tsx
 <ReferenceManyToManyInput
     reference="venues"
@@ -262,6 +315,7 @@ By default, react-admin orders the possible values by `id` desc for the referenc
     {/* ... */}
 </ReferenceManyToManyInput>
 ```
+
 {% endraw %}
 
 ## `source`
@@ -305,16 +359,16 @@ You can specify the columns to use in the associative using the `using` prop.
 
 ## Limitations
 
--   `<ReferenceManyToManyInput>` cannot be used inside an `<ArrayInput>`, a `<ReferenceOneInput>` or a `<ReferenceManyInput>`.
--   `<ReferenceManyToManyInput>` does not support server side validation.
+- `<ReferenceManyToManyInput>` cannot be used inside an `<ArrayInput>`, a `<ReferenceOneInput>` or a `<ReferenceManyInput>`.
+- `<ReferenceManyToManyInput>` does not support server side validation.
 
 ## DataProvider Calls
 
 When rendered, `<ReferenceManyToManyInput>` fetches the `dataProvider` three times in a row:
 
--   once to get the records of the associative resource (`performances` in this case), using a `getManyReference()` call
--   once to get the records of the reference resource (`venues` in this case), using a `getMany()` call.
--   once to get the possible values of the reference resource (`venues` in this case) to show as suggestions in the input, using a `getList()` call
+- once to get the records of the associative resource (`performances` in this case), using a `getManyReference()` call
+- once to get the records of the reference resource (`venues` in this case), using a `getMany()` call.
+- once to get the possible values of the reference resource (`venues` in this case) to show as suggestions in the input, using a `getList()` call
 
 For instance, if the user edits the band of id `123`, `<ReferenceManyToManyInput>` first issues the following query to the `dataProvider`:
 
diff --git a/TreeWithDetails.md b/TreeWithDetails.md
index 9be7e365c88..a5995f6a5cb 100644
--- a/TreeWithDetails.md
+++ b/TreeWithDetails.md
@@ -72,22 +72,23 @@ Check [the `ra-tree` documentation](https://react-admin-ee.marmelab.com/document
 
 ## Props
 
-| Prop                 | Required | Type                   | Default | Description                                                                                 |
-| -------------------- | -------- | ---------------------- | ------- |---------------------------------------------------------------------------------------------|
-| `addRootButton`      | Optional | `ReactNode` or `false` | -       | The create button to add a root node                                                        |
-| `allowMultipleRoots` | Optional | `boolean`              | `false` | To allow trees with multiple roots                                                          |
-| `create`             | Required | `ReactNode`            | -       | The create form of your resource                                                            |
-| `draggable`          | Optional | `boolean`              | `false` | To allow user to reorder nodes                                                              |
-| `edit`               | Required | `ReactNode`            | -       | The edit form of your resource                                                              |
-| `hideRootNodes`      | Optional | `boolean`              | `false` | To hide all root nodes                                                                      |
-| `lazy`               | Optional | `boolean`              | `false` | To load children only when they are expanded                                                |
+| Prop                 | Required | Type                   | Default | Description                                                                                    |
+| -------------------- | -------- | ---------------------- | ------- |----------------------------------------------------------------------------------------------- |
+| `addRootButton`      | Optional | `ReactNode` or `false` | -       | The create button to add a root node                                                           |
+| `allowMultipleRoots` | Optional | `boolean`              | `false` | To allow trees with multiple roots                                                             |
+| `create`             | Required | `ReactNode`            | -       | The create form of your resource                                                               |
+| `draggable`          | Optional | `boolean`              | `false` | To allow user to reorder nodes                                                                 |
+| `edit`               | Required | `ReactNode`            | -       | The edit form of your resource                                                                 |
+| `filter`             | Optional | `object`               | -       | The permanent filter values                                                                    |
+| `hideRootNodes`      | Optional | `boolean`              | `false` | To hide all root nodes                                                                         |
+| `lazy`               | Optional | `boolean`              | `false` | To load children only when they are expanded                                                   |
 | `motion`             | Optional | `boolean`              | `false` | To enable [rc-tree's `<Tree>`](https://github.com/react-component/tree#tree-props) transitions |
-| `nodeActions`        | Optional | `ReactNode`            | -       | To customize the default dropdown action                                                    |
-| `show`               | Required | `ReactNode`            | -       | The show view of your resource                                                              |
-| `showLine`           | Optional | `boolean`              | `false` | Shows a connecting line                                                                     |
-| `sx`                 | Optional | `SxProps`              | -       | Material UI shortcut for defining custom styles                                             |
-| `title`              | Optional | `string`               | -       | The title to display in the `<AppBar>`                                                      |
-| `titleField`         | Optional | `string`               | `title` | Set the record field to display in the tree                                                 |
+| `nodeActions`        | Optional | `ReactNode`            | -       | To customize the default dropdown action                                                       |
+| `show`               | Required | `ReactNode`            | -       | The show view of your resource                                                                 |
+| `showLine`           | Optional | `boolean`              | `false` | Shows a connecting line                                                                        |
+| `sx`                 | Optional | `SxProps`              | -       | Material UI shortcut for defining custom styles                                                |
+| `title`              | Optional | `string`               | -       | The title to display in the `<AppBar>`                                                         |
+| `titleField`         | Optional | `string`               | `title` | Set the record field to display in the tree                                                    |
 
 `<TreeWithDetails>` also accepts the [rc-tree](https://tree-react-component.vercel.app/) props.
 
@@ -244,6 +245,21 @@ If you want to allow user to reorder nodes in the tree, simply add the `draggabl
 export const CategoriesList = () => <TreeWithDetails draggable />;
 ```
 
+
+### `filter`
+
+You can choose to permanently filter the tree to display only a sub tree.
+
+For instance, imagine you have one `employees` resource with a `department` field, and you want to display a tree for the Finance department. Use the `filter` prop to filter the tree:
+
+{% raw %}
+```jsx
+const EmployeeList = () => <TreeWithDetails filter={{ department: 'finance' }} />;
+```
+{% endraw %}
+
+**Note**: This only works if the filter field allows to extract a subtree with its own root node. If you use the `filter` prop to display a sparse selection of nodes (e.g. only the `male` employees), dragging nodes in this tree will not work as expected.
+
 ## `hideRootNodes`
 
 Sometimes, a tree only has one root node for technical reasons and users should probably not see it at all. Use the `hideRootNodes` prop to hide all root nodes.
diff --git a/_data/versions.yml b/_data/versions.yml
index c415472ff14..642b38de1f0 100644
--- a/_data/versions.yml
+++ b/_data/versions.yml
@@ -1,4 +1,4 @@
-- latest (5.4.1)
+- latest (5.4.2)
 - "5.3"
 - "5.2"
 - "5.1"