Feat/update packages across v2 apps

[kemuru]

PR-Codex overview

This PR focuses on updating package dependencies in the web/package.json and yarn.lock files, specifically upgrading versions of @tanstack/react-query, react, and react-dom.

Detailed summary

• Updated @tanstack/react-query from ^4.28.0 to ^5.40.1.
• Updated react from ^18.2.0 to ^18.3.1.
• Updated react-dom from ^18.2.0 to ^18.3.1.
• Updated corresponding versions in yarn.lock.
• Updated @tanstack/query-core version in yarn.lock.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

• New Features
  • Upgraded dependencies to newer versions, potentially enhancing performance and stability.
• Bug Fixes
  • Updated libraries may include various bug fixes from previous versions.

[coderabbitai]

Walkthrough

The pull request updates the package.json file for the @kleros/curate-v2-web project, focusing on dependency version upgrades. The versions of @tanstack/react-query, react, and react-dom have been incremented to their latest releases. No other changes were made to the file's structure or additional dependencies.

Changes

File	Change Summary
web/package.json	- Updated @tanstack/react-query from ^4.28.0 to ^5.40.1
	- Updated react from ^18.2.0 to ^18.3.1
	- Updated react-dom from ^18.2.0 to ^18.3.1

Possibly related PRs

• chore(web): bump-ui-components-library-to-2.15.0 #62: The changes in both PRs involve updates to the package.json file for the same project, indicating a focus on dependency version upgrades, although they target different libraries.

Suggested reviewers

• alcercu

Poem

🐇 In the garden of code, we hop and play,
Upgrading our friends for a brighter day.
React and its kin, now fresh and spry,
With each little change, we reach for the sky!
So let’s celebrate, with joy and cheer,
For every new version brings us near! 🌼

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for curate-v2 ready!

Name	Link
🔨 Latest commit	5395cc0
🔍 Latest deploy log	https://app.netlify.com/sites/curate-v2/deploys/670684cc8c4e9a0008a93318
😎 Deploy Preview	https://deploy-preview-63--curate-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

web/package.json (1)

84-84: Summary of package updates

This PR updates three key dependencies:

1. @tanstack/react-query: ^4.28.0 to ^5.40.1 (major version bump)
2. react: ^18.2.0 to ^18.3.1 (minor version bump)
3. react-dom: ^18.2.0 to ^18.3.1 (minor version bump)

The most critical change is the major version update of @tanstack/react-query, which requires careful attention to potential breaking changes and necessary migrations.

Consider implementing a strategy for managing and documenting dependency updates, such as:

1. Regularly scheduled updates to keep dependencies current.
2. A changelog or update log within the project to track significant dependency changes.
3. Automated testing to catch potential issues introduced by dependency updates early.

Also applies to: 101-101, 103-103

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 21ac0e7 and 5395cc0.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• web/package.json (2 hunks)

🧰 Additional context used

🔇 Additional comments (3)

web/package.json (3)

103-103: Approved: react-dom update to 18.3.1

The update of react-dom from 18.2.0 to 18.3.1 correctly matches the React version update. This is crucial for maintaining compatibility between React and ReactDOM.

Good practice to follow:

1. Always keep react and react-dom versions in sync.
2. Test rendering and DOM-related functionalities thoroughly after the update.

---

84-84: Verify compatibility with @tanstack/react-query v5

The update from v4 to v5 of @tanstack/react-query is a major version bump, which may introduce breaking changes. Please ensure that:

1. The codebase is compatible with v5.
2. Any necessary migrations have been performed.
3. The migration guide has been reviewed and followed.

To help verify the impact of this change, you can run the following script:

---

101-101: Approved: React update to 18.3.1

The update of React from 18.2.0 to 18.3.1 is a minor version bump, which should be backwards compatible. However, it's always a good practice to:

1. Review the React changelog for any new features or potential issues.
2. Test the application thoroughly to ensure no unexpected behavior.

To help verify the impact of this change, you can run the following script:

[alcercu]

lgtm