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.10.4 to 11.13.0 #1314

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

Conversation

X-oss-byte
Copy link
Owner

snyk-top-banner

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

ℹ️ 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 9 versions ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: @emotion/react
  • 11.13.0 - 2024-07-20

    Minor Changes

    • #3198 d8ff8a5 Thanks @ Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.

      Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.

      Default files should continue to work in all environments.

    • #3215 a9f6912 Thanks @ Andarist! - Added edge-light and workerd conditions to package.json manifest to better serve users using Vercel Edge and Cloudflare Workers.

    Patch Changes

    • Updated dependencies [d8ff8a5, a9f6912]:
      • @ emotion/serialize@1.3.0
      • @ emotion/use-insertion-effect-with-fallbacks@1.1.0
      • @ emotion/utils@1.4.0
  • 11.12.0 - 2024-07-19
  • 11.11.4 - 2024-02-27
  • 11.11.3 - 2023-12-23
  • 11.11.1 - 2023-06-07
  • 11.11.0 - 2023-05-06
  • 11.10.8 - 2023-04-28
  • 11.10.6 - 2023-02-16
  • 11.10.5 - 2022-10-27
  • 11.10.4 - 2022-08-30
from @emotion/react GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

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

See this package in npm:
@emotion/react

See this project in Snyk:
https://app.snyk.io/org/sammyfilly/project/fcd0b4c6-4295-48a3-b715-26ca9e08dcda?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Aug 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-js-next-plugin-storybook ❌ Failed (Inspect) Aug 10, 2024 3:07pm
next-js-next-plugin-storybook-g5dx ❌ Failed (Inspect) Aug 10, 2024 3:07pm
next-js-next-plugin-storybook-y5ka ❌ Failed (Inspect) Aug 10, 2024 3:07pm
next-x-storybook ❌ Failed (Inspect) Aug 10, 2024 3:07pm

Copy link

vercel bot commented Aug 10, 2024

Deployment failed with the following error:

Could not parse File as JSON: vercel.json

Copy link

stackblitz bot commented Aug 10, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

changeset-bot bot commented Aug 10, 2024

⚠️ No Changeset found

Latest commit: 2fdbacc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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 ('[Snyk]' found in title). 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.

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