Skip to content

Update dependency react-dom to v18.3.1 #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 26, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-dom (source) 18.2.0 -> 18.3.1 age adoption passing confidence

Release Notes

facebook/react (react-dom)

v18.3.1

Compare Source

  • Export act from react f1338f

v18.3.0

Compare Source

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React
  • Allow writing to this.refs to support string ref codemod 909071
  • Warn for deprecated findDOMNode outside StrictMode c3b283
  • Warn for deprecated test-utils methods d4ea75
  • Warn for deprecated Legacy Context outside StrictMode 415ee0
  • Warn for deprecated string refs outside StrictMode #​25383
  • Warn for deprecated defaultProps for function components #​25699
  • Warn when spreading key #​25697
  • Warn when using act from test-utils d4ea75
React DOM
  • Warn for deprecated unmountComponentAtNode 8a015b
  • Warn for deprecated renderToStaticNodeStream #​28874

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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 this update again.


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

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

Copy link

gitstream-cm bot commented May 26, 2025

🚨 gitStream Monthly Automation Limit Reached 🚨

Your organization has exceeded the number of pull requests allowed for automation with gitStream.
Monthly PRs automated: 420/250

To continue automating your PR workflows and unlock additional features, please contact LinearB.

Copy link

sourcery-ai bot commented May 26, 2025

Reviewer's Guide

Upgrade react-dom from v18.2.0 to v18.3.1 by updating the project dependency specifier in package.json and regenerating the pnpm lockfile to refresh version entries, integrity hashes, and transitive references.

Class Diagram: Key API Changes in react-dom 18.3.1 & Related React 18.3.x Updates

classDiagram
    class ReactDOM_v18_3_1 {
        <<Package: react-dom>>
        version: "18.3.1 (from 18.2.0)"
        unmountComponentAtNode() void : "now issues warning"
        renderToStaticNodeStream() ReadableStream : "now issues warning"
    }

    class React_v18_3_x {
        <<Package: react>>
        version: "18.3.x (accompanies react-dom update)"
        act() void : "newly exported from 'react' module"
        findDOMNode() Element : "now issues warning"
        LegacyContext_usage : "now issues warning"
        stringRefs_usage : "now issues warning"
        defaultProps_for_function_components_usage : "now issues warning"
        test_utils_act_usage : "from 'react-dom/test-utils' now issues warning"
    }

    ReactDOM_v18_3_1 ..> React_v18_3_x : "updated in conjunction with"
Loading

Flow Diagram: Updating react-dom Dependency to v18.3.1

graph LR
    A[Start: project uses react-dom v18.2.0] --> B{Edit package.json};
    B -- "Update react-dom specifier to 18.3.1" --> C[package.json Modified];
    C --> D{Run package manager};
    D -- "pnpm install / update" --> E[pnpm-lock.yaml Regenerated];
    E --> F[Finish: project uses react-dom v18.3.1];

    subgraph "File Changes"
        C
        E
    end
Loading

File-Level Changes

Change Details Files
Upgrade react-dom specifier to v18.3.1
  • Change react-dom version in package.json from 18.2.0 to 18.3.1
web_dashboard/package.json
Regenerate pnpm lockfile for react-dom bump
  • Update importers’ react-dom specifier and version fields
  • Replace react-dom resolution entry with new integrity hash
  • Refresh transitive references in snapshot entries (e.g., styled-components, next, headlessui, tanstack)
web_dashboard/pnpm-lock.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

coderabbitai bot commented May 26, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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 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.

Copy link

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: 🧪 Build Next.js (pnpm)

Failed stage: 🟣 Setup Node.js [❌]

Failure summary:

The action failed because the pnpm executable could not be found in the system. The error message
indicates that the workflow is trying to use pnpm as the package manager (as specified in the cache
configuration for Node.js setup), but pnpm is not installed or not available in the PATH environment
variable.

Relevant error logs:
1:  ##[group]Operating System
2:  Ubuntu
...

123:  c948be9587f204e8f390d87dc46881a9c92d9f86
124:  ##[group]Run actions/setup-node@v4
125:  with:
126:  node-version: 20
127:  cache: pnpm
128:  always-auth: false
129:  check-latest: false
130:  token: ***
131:  ##[endgroup]
132:  Found in cache @ /opt/hostedtoolcache/node/20.19.1/x64
133:  ##[group]Environment details
134:  node: v20.19.1
135:  npm: 10.8.2
136:  yarn: 1.22.22
137:  ##[endgroup]
138:  ##[error]Unable to locate executable file: pnpm. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
139:  Post job cleanup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants