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.13.0 to 11.13.3 #34

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

Conversation

mayrbenjamin92
Copy link
Contributor

Snyk has created this PR to upgrade @emotion/react from 11.13.0 to 11.13.3.

ℹ️ 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 2 months ago, on 2024-08-21.
Release notes
Package name: @emotion/react
  • 11.13.3 - 2024-08-21

    Patch Changes

    • #3232 0ce3ed0 Thanks @ ENvironmentSet! - Distribute css prop attachment over props that are union types

    • Updated dependencies []:

      • @ emotion/serialize@1.3.1
  • 11.13.0 - 2024-07-20
from @emotion/react GitHub release notes
Commit messages
Package name: @emotion/react
  • 3f46884 Version Packages (#3235)
  • 153cf88 Add scale property as unitless (#3240)
  • 0ce3ed0 Distribute `css` prop attachment over props that are union types (#3232)
  • e819f9c Version Packages (#3229)
  • 49f7435 Fix broken browser file reference in primitives-core/package.json (#3228)
  • c6f01a2 Version Packages (#3224)
  • c72d279 Remove incorrect tripleslash directives referencing node types (#3219)

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.

2 participants