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

   Bumps [markdown-to-jsx](https://github.com/quantizor/markdown-to-jsx) from 
9.6.0 to 9.6.1.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/quantizor/markdown-to-jsx/releases";>markdown-to-jsx's 
releases</a>.</em></p>
   <blockquote>
   <h2>v9.6.1</h2>
   <h3>Patch Changes</h3>
   <ul>
   <li>
   <p>9bf4bad: Fix: Jest test suites failing with &quot;Unexpected token 
'export'&quot; when using the library with jsdom environment. The 
<code>browser</code> condition in the package.json <code>imports</code> field 
now correctly provides both ESM (<code>import</code>) and CJS 
(<code>require</code>) sub-conditions, ensuring Jest resolves to the CommonJS 
version of the browser entities module.</p>
   <p>修复:当在 jsdom 环境中使用该库时,Jest 测试套件会因&quot;Unexpected token 
'export'&quot;而失败。package.json <code>imports</code> 字段中的 <code>browser</code> 
条件现在正确提供 ESM(<code>import</code>)和 CJS(<code>require</code>)子条件,确保 Jest 
解析到浏览器实体模块的 CommonJS 版本。</p>
   <p>फिक्स: jsdom वातावरण में लाइब्रेरी का उपयोग करते समय Jest टेस्ट सुइट 
&quot;Unexpected token 'export'&quot; त्रुटि के साथ विफल हो रहे थे। 
package.json <code>imports</code> फ़ील्ड में <code>browser</code> कंडीशन अब सही 
ढंग से ESM (<code>import</code>) और CJS (<code>require</code>) सब-कंडीशन प्रदान 
करती है, जिससे Jest ब्राउज़र एंटिटी मॉड्यूल के CommonJS संस्करण को सही ढंग से 
रिज़ॉल्व करता है।</p>
   </li>
   <li>
   <p>2432f0b: Fix: preserve camelCase attribute casing for all HTML/JSX tags, 
not just PascalCase components. This restores expected behavior where 
attributes like <code>userId</code> and <code>firstName</code> are no longer 
lowercased to <code>userid</code> and <code>firstname</code>.</p>
   <p>修复:为所有 HTML/JSX 标签保留 camelCase 属性大小写,而不仅仅是 PascalCase 组件。这恢复了预期行为,使得 
<code>userId</code> 和 <code>firstName</code> 等属性不再被转换为小写的 <code>userid</code> 和 
<code>firstname</code>。</p>
   <p>फिक्स: सभी HTML/JSX टैग के लिए camelCase एट्रिब्यूट केसिंग को संरक्षित 
करें, न कि केवल PascalCase कंपोनेंट के लिए। यह अपेक्षित व्यवहार को बहाल करता है 
जहां <code>userId</code> और <code>firstName</code> जैसे एट्रिब्यूट अब लोअरकेस 
<code>userid</code> और <code>firstname</code> में परिवर्तित नहीं होते हैं।</p>
   </li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/quantizor/markdown-to-jsx/blob/main/CHANGELOG.md";>markdown-to-jsx's
 changelog</a>.</em></p>
   <blockquote>
   <h2>9.6.1</h2>
   <h3>Patch Changes</h3>
   <ul>
   <li>
   <p>9bf4bad: Fix: Jest test suites failing with &quot;Unexpected token 
'export'&quot; when using the library with jsdom environment. The 
<code>browser</code> condition in the package.json <code>imports</code> field 
now correctly provides both ESM (<code>import</code>) and CJS 
(<code>require</code>) sub-conditions, ensuring Jest resolves to the CommonJS 
version of the browser entities module.</p>
   <p>修复:当在 jsdom 环境中使用该库时,Jest 测试套件会因&quot;Unexpected token 
'export'&quot;而失败。package.json <code>imports</code> 字段中的 <code>browser</code> 
条件现在正确提供 ESM(<code>import</code>)和 CJS(<code>require</code>)子条件,确保 Jest 
解析到浏览器实体模块的 CommonJS 版本。</p>
   <p>फिक्स: jsdom वातावरण में लाइब्रेरी का उपयोग करते समय Jest टेस्ट सुइट 
&quot;Unexpected token 'export'&quot; त्रुटि के साथ विफल हो रहे थे। 
package.json <code>imports</code> फ़ील्ड में <code>browser</code> कंडीशन अब सही 
ढंग से ESM (<code>import</code>) और CJS (<code>require</code>) सब-कंडीशन प्रदान 
करती है, जिससे Jest ब्राउज़र एंटिटी मॉड्यूल के CommonJS संस्करण को सही ढंग से 
रिज़ॉल्व करता है।</p>
   </li>
   <li>
   <p>2432f0b: Fix: preserve camelCase attribute casing for all HTML/JSX tags, 
not just PascalCase components. This restores expected behavior where 
attributes like <code>userId</code> and <code>firstName</code> are no longer 
lowercased to <code>userid</code> and <code>firstname</code>.</p>
   <p>修复:为所有 HTML/JSX 标签保留 camelCase 属性大小写,而不仅仅是 PascalCase 组件。这恢复了预期行为,使得 
<code>userId</code> 和 <code>firstName</code> 等属性不再被转换为小写的 <code>userid</code> 和 
<code>firstname</code>。</p>
   <p>फिक्स: सभी HTML/JSX टैग के लिए camelCase एट्रिब्यूट केसिंग को संरक्षित 
करें, न कि केवल PascalCase कंपोनेंट के लिए। यह अपेक्षित व्यवहार को बहाल करता है 
जहां <code>userId</code> और <code>firstName</code> जैसे एट्रिब्यूट अब लोअरकेस 
<code>userid</code> और <code>firstname</code> में परिवर्तित नहीं होते हैं।</p>
   </li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/quantizor/markdown-to-jsx/commit/fe97715ad31d947b120547923d8ec0a6716504a4";><code>fe97715</code></a>
 Version Packages (<a 
href="https://redirect.github.com/quantizor/markdown-to-jsx/issues/802";>#802</a>)</li>
   <li><a 
href="https://github.com/quantizor/markdown-to-jsx/commit/6adde04f51fcf5897bb858984504625e7993f98f";><code>6adde04</code></a>
 [WIP] Expand translations in preserve attribute casing file (<a 
href="https://redirect.github.com/quantizor/markdown-to-jsx/issues/804";>#804</a>)</li>
   <li><a 
href="https://github.com/quantizor/markdown-to-jsx/commit/9bf4badf3441225b74af258db40b6c55926f0830";><code>9bf4bad</code></a>
 fix: jest &quot;Unexpected token 'export'&quot; error with jsdom environment 
(<a 
href="https://redirect.github.com/quantizor/markdown-to-jsx/issues/803";>#803</a>)</li>
   <li><a 
href="https://github.com/quantizor/markdown-to-jsx/commit/2432f0b7772dd9ee83a448fb06e9822fa0819400";><code>2432f0b</code></a>
 fix: camelCase props correctly preserved for JSX components (<a 
href="https://redirect.github.com/quantizor/markdown-to-jsx/issues/801";>#801</a>)</li>
   <li>See full diff in <a 
href="https://github.com/quantizor/markdown-to-jsx/compare/v9.6.0...v9.6.1";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=markdown-to-jsx&package-manager=npm_and_yarn&previous-version=9.6.0&new-version=9.6.1)](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 show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@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