Skip to content
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

fix(deps): update react monorepo #3183

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 26, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 17.0.52 -> 17.0.83 age adoption passing confidence
@types/react-dom (source) 17.0.17 -> 17.0.26 age adoption passing confidence
eslint-plugin-react-hooks (source) 4.6.0 -> 4.6.2 age adoption passing confidence
react-refresh (source) ^0.14.0 -> ^0.16.0 age adoption passing confidence

Release Notes

facebook/react (eslint-plugin-react-hooks)

v4.6.2

Compare Source

v4.6.1

Compare Source

facebook/react (react-refresh)

v0.16.0

Compare Source

v0.14.2

Compare Source

React DOM
  • Fixed bug with development build preventing events from firing in some versions of Internet Explorer & Edge
  • Fixed bug with development build when using es5-sham in older versions of Internet Explorer
  • Added support for integrity attribute
  • Fixed bug resulting in children prop being coerced to a string for custom elements, which was not the desired behavior
  • Moved react from dependencies to peerDependencies to match expectations and align with react-addons-* packages

v0.14.1

Compare Source

React

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

Summary by Sourcery

Enhancements:

  • Update react-refresh dependency from ^0.14.0 to ^0.16.0 in packages/cli/package.json.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 26, 2024
Copy link

codesandbox bot commented Dec 26, 2024

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

Copy link

restack-app bot commented Dec 26, 2024

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

Copy link

sourcery-ai bot commented Dec 26, 2024

Reviewer's Guide by Sourcery

This PR updates several dependencies related to React and its ecosystem. The most significant changes include updating react-refresh to ^0.16.0, @types/react to 17.0.83, @types/react-dom to 17.0.26, and eslint-plugin-react-hooks to 4.6.2.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated react-refresh to ^0.16.0.
  • The version of react-refresh was updated from ^0.14.0 to ^0.16.0 in the package.json file.
packages/cli/package.json
Updated @types/react to 17.0.83.
  • The version of @types/react was updated from 17.0.52 to 17.0.83 in the package.json file.
packages/cli/package.json
Updated @types/react-dom to 17.0.26.
  • The version of @types/react-dom was updated from 17.0.17 to 17.0.26 in the package.json file.
packages/cli/package.json
Updated eslint-plugin-react-hooks to 4.6.2.
  • The version of eslint-plugin-react-hooks was updated from 4.6.0 to 4.6.2 in the package.json file.
packages/cli/package.json

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.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a 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. You can also use
    this command to specify where the summary should be inserted.

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

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Copy link

Report too large to display inline

View full report↗︎

Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Critical CVE npm/@babel/[email protected] ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

Copy link

github-actions bot commented Jan 2, 2025

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions bot added the stale label Jan 2, 2025
@github-actions github-actions bot closed this Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants