dependabot[bot] opened a new pull request, #21605:
URL: https://github.com/apache/superset/pull/21605

   Bumps [@emotion/react](https://github.com/emotion-js/emotion) from 11.4.1 to 
11.10.4.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/emotion-js/emotion/releases";><code>@​emotion/react</code>'s
 releases</a>.</em></p>
   <blockquote>
   <h2><code>@​emotion/react</code><a 
href="https://github.com/11";><code>@​11</code></a>.10.4</h2>
   <h3>Patch Changes</h3>
   <ul>
   <li>
   <p><a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/pull/2867";>#2867</a>
 <a 
href="https://github.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a";><code>89b6dbb3</code></a>
 Thanks <a href="https://github.com/Andarist";><code>@​Andarist</code></a>! - 
Externalized code referencing <code>React.useInsertionEffect</code> to a 
separate <code>@emotion/use-insertion-effect-with-fallbacks</code> package. 
This package should be used in your defined externals if you bundle Emotion for 
whatever reason. It references <code>useInsertionEffect</code> in a very 
specific way that allows us to use it conditionally. However, if the code 
consuming Emotion is bundled as a library with Emotion in it then some bundlers 
might change the way in which we reference <code>useInsertionEffect</code> and 
that might create problems for bundlers used to consume the said library code. 
By externalizing this new package you can still bundle Emotion if you want to 
without runn
 ing into this problem as you won't &quot;destroy&quot; the carefully crafted 
reference to <code>useInsertionEffect</code> in the process.</p>
   <p>Note that we don't recommend bundling Emotion. You should have very 
specific reasons to do so.</p>
   </li>
   <li>
   <p>Updated dependencies [<a 
href="https://github.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a";><code>89b6dbb3</code></a>]:</p>
   <ul>
   <li><code>@​emotion/use-insertion-effect-with-fallbacks</code><a 
href="https://github.com/1";><code>@​1</code></a>.0.0</li>
   </ul>
   </li>
   </ul>
   <h2><code>@​emotion/react</code><a 
href="https://github.com/11";><code>@​11</code></a>.10.0</h2>
   <h3>Minor Changes</h3>
   <ul>
   <li>
   <p><a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/pull/2819";>#2819</a>
 <a 
href="https://github.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228";><code>bbad8c79</code></a>
 Thanks <a 
href="https://github.com/nicksrandall";><code>@​nicksrandall</code></a>! - 
<code>exports</code> field has been added to the <code>package.json</code> 
manifest. It limits what files can be imported from a package but we've tried 
our best to allow importing all the files that were considered to be a part of 
the public API.</p>
   </li>
   <li>
   <p><a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/pull/2819";>#2819</a>
 <a 
href="https://github.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228";><code>bbad8c79</code></a>
 Thanks <a 
href="https://github.com/nicksrandall";><code>@​nicksrandall</code></a>! - 
Thanks to the added <code>exports</code> field, the package now includes a 
<code>worker</code> condition that can be utilized by properly configured 
bundlers when targeting worker-like environments. It fixes the issue with 
browser-specific files being prioritized by some bundlers when targeting 
workers.</p>
   </li>
   </ul>
   <h3>Patch Changes</h3>
   <ul>
   <li>Updated dependencies [<a 
href="https://github.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228";><code>bbad8c79</code></a>,
 <a 
href="https://github.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228";><code>bbad8c79</code></a>]:
   <ul>
   <li><code>@​emotion/babel-plugin</code><a 
href="https://github.com/11";><code>@​11</code></a>.10.0</li>
   <li><code>@​emotion/cache</code><a 
href="https://github.com/11";><code>@​11</code></a>.10.0</li>
   <li><code>@​emotion/serialize</code><a 
href="https://github.com/1";><code>@​1</code></a>.1.0</li>
   <li><code>@​emotion/utils</code><a 
href="https://github.com/1";><code>@​1</code></a>.2.0</li>
   <li><code>@​emotion/weak-memoize</code><a 
href="https://github.com/0";><code>@​0</code></a>.3.0</li>
   </ul>
   </li>
   </ul>
   <h2><code>@​emotion/react</code><a 
href="https://github.com/11";><code>@​11</code></a>.9.3</h2>
   <h3>Patch Changes</h3>
   <ul>
   <li>
   <p><a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/pull/2766";>#2766</a>
 <a 
href="https://github.com/emotion-js/emotion/commit/5b3f4d78d54552f9785836bc2cc56d3f789afc47";><code>5b3f4d78</code></a>
 Thanks <a href="https://github.com/Andarist";><code>@​Andarist</code></a>! - 
<code>ThemeProviderProps[&quot;children&quot;]</code> was marked as a required 
prop as <code>ThemeProvider</code> should always wrap some subtree.</p>
   </li>
   <li>
   <p>Updated dependencies [<a 
href="https://github.com/emotion-js/emotion/commit/26e4e3e8b68479f0e3cb8fbec723da47afd6ac98";><code>26e4e3e8</code></a>,
 <a 
href="https://github.com/emotion-js/emotion/commit/6c2d7a6010af85502ae33d14dcbd3bb62ed7612e";><code>6c2d7a60</code></a>,
 <a 
href="https://github.com/emotion-js/emotion/commit/5e81f213980e9ba2cfa35256476673b68d47fc33";><code>5e81f213</code></a>]:</p>
   <ul>
   <li><code>@​emotion/serialize</code><a 
href="https://github.com/1";><code>@​1</code></a>.0.4</li>
   <li><code>@​emotion/cache</code><a 
href="https://github.com/11";><code>@​11</code></a>.9.3</li>
   </ul>
   </li>
   </ul>
   <h2><code>@​emotion/react</code><a 
href="https://github.com/11";><code>@​11</code></a>.9.0</h2>
   <h3>Patch Changes</h3>
   <ul>
   <li>
   <p><a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/pull/2700";>#2700</a>
 <a 
href="https://github.com/emotion-js/emotion/commit/d935762131b1474f2474296ee4706f7ecd59b6dd";><code>d9357621</code></a>
 Thanks <a 
href="https://github.com/arturmuller";><code>@​arturmuller</code></a>! - Fixed a 
false positive warning for <code>content</code> properties that included 
<code>var()</code>.</p>
   </li>
   <li>
   <p>Updated dependencies [<a 
href="https://github.com/emotion-js/emotion/commit/d935762131b1474f2474296ee4706f7ecd59b6dd";><code>d9357621</code></a>]:</p>
   <ul>
   <li><code>@​emotion/serialize</code><a 
href="https://github.com/1";><code>@​1</code></a>.0.3</li>
   </ul>
   </li>
   </ul>
   <h2><code>@​emotion/react</code><a 
href="https://github.com/11";><code>@​11</code></a>.8.2</h2>
   <h3>Patch Changes</h3>
   <ul>
   <li><a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/pull/2677";>#2677</a>
 <a 
href="https://github.com/emotion-js/emotion/commit/ff3cb16419b44578c7bab275dce7b5845b61db84";><code>ff3cb164</code></a>
 Thanks <a href="https://github.com/Jack-Works";><code>@​Jack-Works</code></a>! 
- Change <code>Global</code> component to use the <code>StyleSheet</code> 
constructor of the current <code>cache.sheet</code>. This is useful when 
<code>cache.sheet</code> is not the default implementation. Thanks to that the 
inner sheet constructed by <code>Global</code> can share the behavior with its 
&quot;main&quot; sheet that is hold by the <code>cache</code>.</li>
   </ul>
   <h2><code>@​emotion/react</code><a 
href="https://github.com/11";><code>@​11</code></a>.8.1</h2>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/6835850e39a5df4324e1f4ff4874fdce3d5b51d5";><code>6835850</code></a>
 Version Packages (<a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/issues/2872";>#2872</a>)</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a";><code>89b6dbb</code></a>
 Move conditional <code>useInsertionEffect</code> declarations into separate 
package (<a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/issues/2867";>#2867</a>)</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/28522cd3cad82c25a896b64418aa99ef767e03b2";><code>28522cd</code></a>
 Upgrade Yarn (<a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/issues/2870";>#2870</a>)</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/f2608b3a542164a3622453f306e2b782929a3020";><code>f2608b3</code></a>
 Version Packages (<a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/issues/2865";>#2865</a>)</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/b9b8b7493d6aea7cb2543aa1925eb2cac9636be9";><code>b9b8b74</code></a>
 Fixed a regression that could cause a crash when looking for an ignoring 
comm...</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/c60d646ff56ddaaee5d62a619276ae214db2a604";><code>c60d646</code></a>
 Version Packages (<a 
href="https://github-redirect.dependabot.com/emotion-js/emotion/issues/2860";>#2860</a>)</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/df434eaf9d9ea9b3e574a576f7f93a533f70476b";><code>df434ea</code></a>
 Pass <code>--no-immutable</code> to Yarn when regenerating lockfile after 
versioning pac...</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/2de94aee23552d9f2d93f594671359f11c0babff";><code>2de94ae</code></a>
 Regenerate lockfile after versioning packages</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/005e211d53a4a1a34509400e41402b8910875fda";><code>005e211</code></a>
 Fixed an issue in the styles minifier that caused interpolations to be 
someti...</li>
   <li><a 
href="https://github.com/emotion-js/emotion/commit/0ffd6068fe1c455788c0099b350ea771ce5657ee";><code>0ffd606</code></a>
 Fixed the ignore flag not disabling the warning when there are multiple 
block...</li>
   <li>Additional commits viewable in <a 
href="https://github.com/emotion-js/emotion/compare/@emotion/[email protected]...@emotion/[email protected]";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@emotion/react&package-manager=npm_and_yarn&previous-version=11.4.1&new-version=11.10.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to