@payloadcms/plugin-search 3.0.0-beta.75 on Node.js NPM

v3.0.0-beta.75 (2024-08-07)

db-*: allows for running migrations in production automatically (#7563) (1cb1e5e)
bump next canary to 104 and update withPayload for new config (#7541) (8d1fc6e)
richtext-lexical: export serialized inline blocks and table node types (ffd8ea5)

db-postgres: #7492 migrate snapshots (#7540) (46f70d9)
plugin-seo: issue with generating image from a function (#7566) (b7e2c59)
hydrate permissions on dashboard, fix active menu item logic (0cc7184)
ui: fixes issue when filtering by checkbox value in a different language (#7547) (4a20a63)
next, payload: enable relationship & upload version tracking when localization enabled (#7508) (62744e7)
richtext-lexical: html converters not respecting overrideAccess property when populating values, in local API (c15d679)
scopes preferences queries and mutations by user (#7534) (a422a0d)
ensure pw confirmation when creating users in admin panel (#7535) (edaeb1e)
custom meta icons getting overwritten by default icon (#7466) (6f35c35)

adjusts auth hydration from server (#7545) (e905675)
Fixes #6823
Allows the server to initialize the AuthProvider via props. Renames
HydrateClientUser to HydrateAuthProvider. It now only hydrates the
permissions as the user can be set from props. Permissions can be
initialized from props, but still need to be hydrated for some pages as
access control can be specific to docs/lists etc.
- Renames exported HydrateClientUser to HydrateAuthProvider
⚠️ bump next canary to 104 and update withPayload for new config (#7541) (8d1fc6e)
We are now bumping up the Next canary version to 15.0.0-canary.104 and
react and react-dom to ^19.0.0-rc-06d0b89e-20240801.
Your new dependencies should look like this:
```
"next": "15.0.0-canary.104",
"react": "^19.0.0-rc-06d0b89e-20240801",
"react-dom": "^19.0.0-rc-06d0b89e-20240801",
```
richtext-lexical: html converters not respecting overrideAccess property when populating values, in local API (c15d679)