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

   Bumps 
[@next/bundle-analyzer](https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer)
 from 14.2.32 to 16.2.4.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/vercel/next.js/releases";>@​next/bundle-analyzer's 
releases</a>.</em></p>
   <blockquote>
   <h2>v16.2.4</h2>
   <blockquote>
   <p>[!NOTE]
   This release is backporting bug fixes. It does <strong>not</strong> include 
all pending features/changes on canary.</p>
   </blockquote>
   <h3>Core Changes</h3>
   <ul>
   <li>chore: Bump reqwest to 0.13.2 (Fixes Google Fonts with Turbopack for 
Windows on ARM64) (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92713";>#92713</a>)</li>
   <li>Turbopack: fix filesystem watcher config not applying 
follow_symlinks(false) (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92631";>#92631</a>)</li>
   <li>Scope Safari ?ts= cache-buster to CSS/font assets only (Pages Router) 
(<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92580";>#92580</a>)</li>
   <li>Compiler: Support boolean and number primtives in next.config defines 
(<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92731";>#92731</a>)</li>
   <li>turbo-tasks: Fix recomputation loop by allowing cell cleanup on error 
during recomputation (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92725";>#92725</a>)</li>
   <li>Turbopack: shorter error for ChunkGroupInfo::get_index_of (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92814";>#92814</a>)</li>
   <li>Turbopack: shorter error message for ModuleBatchesGraph::get_entry_index 
(<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92828";>#92828</a>)</li>
   <li>Adding more system info to the 'initialize project' trace (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92427";>#92427</a>)</li>
   </ul>
   <h3>Credits</h3>
   <p>Huge thanks to <a 
href="https://github.com/Badbird5907";><code>@​Badbird5907</code></a>, <a 
href="https://github.com/lukesandberg";><code>@​lukesandberg</code></a>, <a 
href="https://github.com/andrewimm";><code>@​andrewimm</code></a>, <a 
href="https://github.com/sokra";><code>@​sokra</code></a>, and <a 
href="https://github.com/mischnic";><code>@​mischnic</code></a> for helping!</p>
   <h2>v16.2.3</h2>
   <blockquote>
   <p>[!NOTE]
   This release is backporting security and bug fixes. For more information 
about the fixed security vulnerability, please see <a 
href="https://vercel.com/changelog/summary-of-cve-2026-23869";>https://vercel.com/changelog/summary-of-cve-2026-23869</a>.
 The release does <strong>not</strong> include all pending features/changes on 
canary.</p>
   </blockquote>
   <h3>Core Changes</h3>
   <ul>
   <li>Ensure app-page reports stale ISR revalidation errors via onRequestError 
(<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92282";>#92282</a>)</li>
   <li>Fix [Bug]: manifest.ts breaks HMR in Next.js 16.2 (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/91981";>#91981</a>
 through <a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92273";>#92273</a>)</li>
   <li>Deduplicate output assets and detect content conflicts on emit (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92292";>#92292</a>)</li>
   <li>Fix styled-jsx race condition: styles lost due to concurrent rendering 
(<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92459";>#92459</a>)</li>
   <li>turbo-tasks-backend: stability fixes for task cancellation and error 
handling (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92254";>#92254</a>)</li>
   </ul>
   <h3>Credits</h3>
   <p>Huge thanks to <a 
href="https://github.com/icyJoseph";><code>@​icyJoseph</code></a>, <a 
href="https://github.com/sokra";><code>@​sokra</code></a>, <a 
href="https://github.com/wbinnssmith";><code>@​wbinnssmith</code></a>, <a 
href="https://github.com/eps1lon";><code>@​eps1lon</code></a> and <a 
href="https://github.com/ztanner";><code>@​ztanner</code></a> for helping!</p>
   <h2>v16.2.2</h2>
   <blockquote>
   <p>[!NOTE]
   This release is backporting bug fixes. It does <strong>not</strong> include 
all pending features/changes on canary.</p>
   </blockquote>
   <h3>Core Changes</h3>
   <ul>
   <li>backport: Move expanded adapters docs to API reference (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92115";>#92115</a>)
 (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92129";>#92129</a>)</li>
   <li>Backport: TypeScript v6 deprecations for baseUrl and moduleResolution 
(<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92130";>#92130</a>)</li>
   <li>[create-next-app] Skip interactive prompts when CLI flags are provided 
(<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/91840";>#91840</a>)</li>
   <li>next.config.js: Accept an option for serverFastRefresh (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/91968";>#91968</a>)</li>
   <li>Turbopack: enable server HMR for app route handlers (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/91466";>#91466</a>)</li>
   <li>Turbopack: exclude metadata routes from server HMR (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92034";>#92034</a>)</li>
   <li>Fix CI for glibc linux builds</li>
   <li>Backport: disable bmi2 in qfilter <a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92177";>#92177</a></li>
   <li>[backport] Fix CSS HMR on Safari (<a 
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/92174";>#92174</a>)</li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/vercel/next.js/commit/2275bd8598c88e8652d1271e74bcf972f72f4f38";><code>2275bd8</code></a>
 v16.2.4</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/d5f649b2f4affdad1009cb178c1e3b37f4f1ad3f";><code>d5f649b</code></a>
 v16.2.3</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/52faae3d94641584e13691238df5be158d0f00fb";><code>52faae3</code></a>
 v16.2.2</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/ed7d2cef246dcb3e2955c018fd8b2027e0ff8eed";><code>ed7d2ce</code></a>
 v16.2.1</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/c5c94dffbf084e66b172a9c6ff23d80c24973764";><code>c5c94df</code></a>
 v16.2.0</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/3683192a6bea9011222e9b236f8000b5266f3fe6";><code>3683192</code></a>
 v16.2.0-canary.104</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/668981482a3f9de97c4c1371e940e0f84972c080";><code>6689814</code></a>
 v16.2.0-canary.103</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/ad66dbc89b356867c308110dc5365a696c763991";><code>ad66dbc</code></a>
 v16.2.0-canary.102</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/b8564984305ff0f4feb9e7f709652a735b89aa0a";><code>b856498</code></a>
 v16.2.0-canary.101</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/136b77e4d971de868b56066e714c1f187af6cb23";><code>136b77e</code></a>
 v16.2.0-canary.100</li>
   <li>Additional commits viewable in <a 
href="https://github.com/vercel/next.js/commits/v16.2.4/packages/next-bundle-analyzer";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   <details>
   <summary>Most Recent Ignore Conditions Applied to This Pull Request</summary>
   
   | Dependency Name | Ignore Conditions |
   | --- | --- |
   | @next/bundle-analyzer | [>= 15.a, < 16] |
   </details>
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@next/bundle-analyzer&package-manager=npm_and_yarn&previous-version=14.2.32&new-version=16.2.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 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]

Reply via email to