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

[Snyk] Upgrade @emotion/react from 11.11.3 to 11.11.4 #11

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

Conversation

john-dot-oa
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @emotion/react from 11.11.3 to 11.11.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2024-02-27.
Release notes
Package name: @emotion/react
  • 11.11.4 - 2024-02-27

    Patch Changes

    • #3159 5b82631d Thanks @ iegik! - Renamed an internal hasOwnProperty to hasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution with Object.freeze(Object.prototype).
  • 11.11.3 - 2023-12-23

    Patch Changes

    • #3101 49c20b4f Thanks @ kyvong! - Fix Theme import for newer Typescript module resolution modes

    • Updated dependencies [45c440fb]:

      • @ emotion/serialize@1.1.3
from @emotion/react GitHub release notes
Commit messages
Package name: @emotion/react
  • 6e0e388 Version Packages (#3160)
  • 5b82631 Renamed an internal `hasOwnProperty` to `hasOwn` (#3159)
  • 0bfa978 Add `disableRemotePlayback` to valid prop types (#3156)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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.

None yet

2 participants