build(frontend): bump mobx-react

[magicznyleszek]

💭 Notes

Bump mobx-react to a version that is React v19 ready.

[Copilot]

Pull request overview

Updates the frontend dependency tree to make mobx-react “React v19 ready” by upgrading to the latest major version and updating the lockfile accordingly.

Changes:

• Bump mobx-react from ^7.6.0 to ^9.2.2.
• Update package-lock.json to reflect the new mobx-react / mobx-react-lite versions and their transitive dependencies (including use-sync-external-store).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updates the declared mobx-react dependency version.
package-lock.json	Updates resolved versions/metadata for mobx-react, mobx-react-lite, and transitive deps to match the upgrade.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[greptile-apps]

Greptile Summary

The PR upgrades mobx-react from 7.6.0 to 9.2.2 to add React 19 compatibility.

• Updates the direct dependency and lockfile.
• Upgrades mobx-react-lite transitively and makes use-sync-external-store a production dependency.
• The PR description does not follow the repository template.

Confidence Score: 4/5

The dependency update appears safe to merge, with the non-blocking requirement that the PR description be completed using the repository template.

The manifest and lockfile consistently resolve the upgraded dependency graph, and no concrete build or runtime incompatibility was established; the remaining issue is incomplete review documentation.

Files Needing Attention: package.json

_{Reviews (1): Last reviewed commit: "bump mobx-react" | Re-trigger Greptile}

[greptile-apps]

Complete the PR description

This major dependency upgrade is documented using only the Notes section, omitting the repository template's required checklist, summary, description, and validation information and leaving reviewers and changelog maintainers without the expected context.

Rule Used: What: PR descriptions must follow the repository's... (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!