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

   Bumps 
[vue-i18n](https://github.com/intlify/vue-i18n/tree/HEAD/packages/vue-i18n) 
from 10.0.4 to 10.0.6.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/intlify/vue-i18n/releases";>vue-i18n's 
releases</a>.</em></p>
   <blockquote>
   <h2>v10.0.6</h2>
   <!-- raw HTML omitted -->
   <h2>What's Changed</h2>
   <h3>🔒 Security Fixes</h3>
   <ul>
   <li>fix: prototype pollution in <code>handleFlatJson</code>, about details 
see <a 
href="https://github.com/intlify/vue-i18n/security/advisories/GHSA-p2ph-7g93-hw3m";>https://github.com/intlify/vue-i18n/security/advisories/GHSA-p2ph-7g93-hw3m</a></li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/intlify/vue-i18n/compare/v10.0.5...v10.0.6";>https://github.com/intlify/vue-i18n/compare/v10.0.5...v10.0.6</a></p>
   <h2>v10.0.5</h2>
   <!-- raw HTML omitted -->
   <h2>What's Changed</h2>
   <h3>🔒 Security Fixes</h3>
   <ul>
   <li>fix: XSS vulnerability with prototype pollution on AST: <a 
href="https://github.com/intlify/vue-i18n/security/advisories/GHSA-9r9m-ffp6-9x4v";>https://github.com/intlify/vue-i18n/security/advisories/GHSA-9r9m-ffp6-9x4v</a></li>
   <li>fix: prototype pollusion on deepCopy: <a 
href="https://github.com/intlify/vue-i18n/security/advisories/GHSA-hjwq-mjwj-4x6c";>https://github.com/intlify/vue-i18n/security/advisories/GHSA-hjwq-mjwj-4x6c</a></li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/intlify/vue-i18n/compare/v10.0.4...v10.0.5";>https://github.com/intlify/vue-i18n/compare/v10.0.4...v10.0.5</a></p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/intlify/vue-i18n/blob/master/CHANGELOG.md";>vue-i18n's 
changelog</a>.</em></p>
   <blockquote>
   <h1>v11.0.1 (2024-12-26T07:40:58Z)</h1>
   <p>This changelog is generated by <a 
href="https://github.com/intlify/vue-i18n/releases/tag/v11.0.1";>GitHub 
Releases</a></p>
   <!-- raw HTML omitted -->
   <h2>What's Changed</h2>
   <h3>âš¡ Improvement Features</h3>
   <ul>
   <li>fix: v-t custom directive warning when it will run by <a 
href="https://github.com/kazupon";><code>@​kazupon</code></a> in <a 
href="https://redirect.github.com/intlify/vue-i18n/pull/2057";>intlify/vue-i18n#2057</a></li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/intlify/vue-i18n/compare/v11.0.0...v11.0.1";>https://github.com/intlify/vue-i18n/compare/v11.0.0...v11.0.1</a></p>
   <h1>v11.0.0 (2024-12-24T15:01:00Z)</h1>
   <p>This changelog is generated by <a 
href="https://github.com/intlify/vue-i18n/releases/tag/v11.0.0";>GitHub 
Releases</a></p>
   <!-- raw HTML omitted -->
   <h2>What's Changed</h2>
   <h3>Deprecate Legacy API mode</h3>
   <p>The Legacy API mode was the API mode compatible with v8 for Vue 2. When 
v9 was released, the Legacy API was provided to smooth the migration from v8 to 
v9.</p>
   <p>Legacy API mode will be deprecated in v11, as previous vue-i18n releases 
have already provided the following to support migration to Composition API 
mode</p>
   <ul>
   <li>Migration from Legacy API mode to Composition API mode, see the <a 
href="https://vue-i18n.intlify.dev/guide/migration/vue3.html";>docs</a></li>
   <li>Composition API usage, see the <a 
href="https://vue-i18n.intlify.dev/guide/advanced/composition.html";>docs</a></li>
   </ul>
   <p>For compatibility, Legacy API mode still works in v11, but will be 
removed entirely in v12, so Legacy API mode will not work after that 
version.</p>
   <h3>Deprecate Custom Directive <code>v-t</code></h3>
   <p>The advantage of <code>v-t</code> was that it could optimize performance 
using the vue compiler transform and the pre-translation of 
<code>vue-i18n-extension</code>.</p>
   <p>This feature was supported from Vue 2.
   About details see the blog <a 
href="https://medium.com/@kazu_pon/performance-optimization-of-vue-i18n-83099eb45c2d";>article</a></p>
   <p>In Vue 3, due to the Composition API, the pre-translation of <a 
href="https://github.com/intlify/vue-i18n-extensions";><code>vue-i18n-extension</code></a>
 is now limited only for global scope.</p>
   <p>In addition, Vue 3 Virtual DOM optimization has been introduced, and the 
optimization provided by <code>vue-i18n-extension</code> is no longer very 
effective. We need to require settings for SSR, the benefits of using 
<code>v-t</code> have disappeared. And DX of templates using <code>v-t</code> 
is not good. Custom directives do not work with key completion in editors (e.g. 
vscode).</p>
   <p>For compatibility, <code>v-t</code> mode still works in v11, but will be 
removed entirely in v12, so <code>v-t</code> will not work after that 
version.</p>
   <h3>Drop <code>tc</code> and <code>$tc</code> for Legacy API mode</h3>
   <p>These APIs had already deprecated in warning about being dropped in v11. 
docs <a 
href="https://vue-i18n.intlify.dev/guide/migration/breaking10.html#deprecate-tc-and-tc-for-legacy-api-mode";>says</a></p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/intlify/vue-i18n/commit/e40c1601656d7e517fb1a3a84f55bd536a847ffb";><code>e40c160</code></a>
 release: v10.0.6</li>
   <li><a 
href="https://github.com/intlify/vue-i18n/commit/be77fccb0fe2b1834f3b6431fd5036b23470ae9d";><code>be77fcc</code></a>
 release: v10.0.5</li>
   <li>See full diff in <a 
href="https://github.com/intlify/vue-i18n/commits/v10.0.6/packages/vue-i18n";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=vue-i18n&package-manager=npm_and_yarn&previous-version=10.0.4&new-version=10.0.6)](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)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/seatunnel/network/alerts).
   
   </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: commits-unsubscr...@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to