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/styled from 11.10.4 to 11.14.0 #1744

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

Conversation

X-oss-byte
Copy link
Owner

@X-oss-byte X-oss-byte commented Jan 5, 2025

snyk-top-banner

Snyk has created this PR to upgrade @emotion/styled from 11.10.4 to 11.14.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 a month ago.

Release notes
Package name: @emotion/styled
  • 11.14.0 - 2024-12-09

    Minor Changes

    • #3284 a19d019 Thanks @ Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

    Patch Changes

    • Updated dependencies [e1bf17e]:
      • @ emotion/use-insertion-effect-with-fallbacks@1.2.0
  • 11.13.5 - 2024-11-20

    Patch Changes

    • #3270 77d930d Thanks @ emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @ emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

    • Updated dependencies [77d930d]:

      • @ emotion/serialize@1.3.3
      • @ emotion/utils@1.4.2
      • @ emotion/babel-plugin@11.13.5
  • 11.13.0 - 2024-07-20
  • 11.12.0 - 2024-07-19
  • 11.11.5 - 2024-03-29
  • 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/styled 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:

Summary by Sourcery

Build:

  • Upgrade @emotion/styled dependency in the examples/with-emotion project.

Snyk has created this PR to upgrade @emotion/styled from 11.10.4 to 11.14.0.

See this package in npm:
@emotion/styled

See this project in Snyk:
https://app.snyk.io/org/sammytezzy/project/e552070d-761c-4534-80af-af5315acb9f9?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Jan 5, 2025

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) Jan 5, 2025 2:53pm
next-js-next-plugin-storybook-g5dx ❌ Failed (Inspect) Jan 5, 2025 2:53pm
next-js-next-plugin-storybook-y5ka ❌ Failed (Inspect) Jan 5, 2025 2:53pm
next-x-storybook ❌ Failed (Inspect) Jan 5, 2025 2:53pm

Copy link

vercel bot commented Jan 5, 2025

Deployment failed with the following error:

Could not parse File as JSON: vercel.json

Copy link

stackblitz bot commented Jan 5, 2025

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

Copy link

changeset-bot bot commented Jan 5, 2025

⚠️ No Changeset found

Latest commit: 5f41426

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 bot commented Jan 5, 2025

Reviewer's Guide by Sourcery

This PR upgrades @emotion/styled from 11.10.4 to 11.14.0. The upgrade includes migration of the source code to TypeScript, a fix for inconsistent hashes when using development vs production bundles with @emotion/babel-plugin and sourceMap: true, and updated dependencies.

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

File-Level Changes

Change Details Files
Upgraded @emotion/styled from version 11.10.4 to 11.14.0.
  • Updated the @emotion/styled dependency version in package.json.
examples/with-emotion/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 ('[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