fix(deps): update react monorepo to v19 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/react (source)	^18.3.1 -> ^19.0.0
react (source)	^18.3.1 -> ^19.0.0
react-dom (source)	^18.3.1 -> ^19.0.0

---

Release Notes

facebook/react (react)

v19.0.0

Compare Source

facebook/react (react-dom)

v19.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "* * * * 0,6" (UTC), Automerge - "* 0-3 * * *" (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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[woodpecker-bot]

Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-4529.surge.sh

[qwerty287]

@anbraten react 19 seems to be supported? Can we merge this?

[anbraten]

It might work somehow, however peer dependencies are set to the following so I would avoid updating atm to stop it from throwing warnings.

"peerDependencies": {
    "@mdx-js/react": "^3.0.0",
    "react": "^18.0.0",
    "react-dom": "^18.0.0"
  },

[qwerty287]

Which warnings do you mean? There are no in https://ci.woodpecker-ci.org/repos/3780/pipeline/23631/10

[qwerty287]

@anbraten did you see my question?

Which warnings do you mean? There are no in https://ci.woodpecker-ci.org/repos/3780/pipeline/23631/10

[pat-s]

I assume he means that these would throw warnings if the PR gets merged. However, I would expect the peer deps to be updated after that as well, no?

If we don't see any errors atm, I think we should trust our pipelines and checks and move on?

[anbraten]

Any reason we need to push this update? The current React version is still supported. I guess we can just update when the docusaurus team is officially supporting it. At least it is throwing errors in the browser and warnings with pnpm install (doesn't happend in ci as of the frozen lockfile argument) with the new version and might be the reason of the broken search as well.

[pat-s]

No need to push, it is just hanging around and people look at it then and try to resolve it.

As it is a major, it might very well cause issues. It is just important to not forget about it and reconsider it every once in a while once deps have caught up.