dependabot[bot] opened a new pull request, #250:
URL: https://github.com/apache/doris-opentelemetry-demo/pull/250

   Bumps [next](https://github.com/vercel/next.js) from 15.2.1 to 15.5.12.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/vercel/next.js/releases";>next's releases</a>.</em></p>
   <blockquote>
   <h2>v15.5.12</h2>
   <blockquote>
   <p>[!NOTE]
   This release is backporting bug fixes. It does <strong>not</strong> include 
all pending features/changes on canary.</p>
   </blockquote>
   <ul>
   <li>fix unlock in publish-native</li>
   </ul>
   <p>This is a re-release of <a 
href="https://github.com/vercel/next.js/releases/tag/v15.5.11";>v15.5.11</a> 
applying the turbopack changes.</p>
   <h2>v15.5.11</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>Tracing: Fix memory leak in span map (<a 
href="https://redirect.github.com/vercel/next.js/issues/85529";>#85529</a>)</li>
   <li>fix: ensure LRU cache items have minimum size of 1 to prevent unbounded 
growth (<a 
href="https://redirect.github.com/vercel/next.js/issues/89134";>#89134</a>)</li>
   <li>Turbopack: fix NFT tracing of sharp 0.34 (<a 
href="https://redirect.github.com/vercel/next.js/issues/82340";>#82340</a>)</li>
   <li>Turbopack: support pattern into exports field (<a 
href="https://redirect.github.com/vercel/next.js/issues/82757";>#82757</a>)</li>
   <li>NFT tracing fixes (<a 
href="https://redirect.github.com/vercel/next.js/issues/84155";>#84155</a> and 
<a 
href="https://redirect.github.com/vercel/next.js/issues/85323";>#85323</a>)</li>
   <li>Turbopack: validate CSS without computing all paths (<a 
href="https://redirect.github.com/vercel/next.js/issues/83810";>#83810</a>)</li>
   <li>feat: implement LRU cache with invocation ID scoping for minimal mode 
response cache (<a 
href="https://redirect.github.com/vercel/next.js/issues/89129";>#89129</a>)</li>
   </ul>
   <h3>Credits</h3>
   <p>Huge thanks to <a 
href="https://github.com/timneutkens";><code>@​timneutkens</code></a>, <a 
href="https://github.com/mischnic";><code>@​mischnic</code></a>, <a 
href="https://github.com/ztanner";><code>@​ztanner</code></a>, and <a 
href="https://github.com/wyattjoh";><code>@​wyattjoh</code></a> for helping!</p>
   <h2>v15.5.10</h2>
   <p>Please refer the following changelogs for more information about this 
security release:</p>
   <ul>
   <li><a 
href="https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472";>https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472</a></li>
   <li><a 
href="https://vercel.com/changelog/summary-of-cve-2026-23864";>https://vercel.com/changelog/summary-of-cve-2026-23864</a></li>
   </ul>
   <h2>v15.4.11</h2>
   <p>Please see this <a 
href="https://vercel.com/changelog/summary-of-cve-2026-23864";>changelog</a> for 
more information about this security patch.</p>
   <h2>v15.3.9</h2>
   <p>Please see this <a 
href="https://vercel.com/changelog/summary-of-cve-2026-23864";>changelog</a> for 
more information about this security patch.</p>
   <h2>v15.2.9</h2>
   <p>Please see this <a 
href="https://vercel.com/changelog/summary-of-cve-2026-23864";>changelog</a> for 
more information about this security patch.</p>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/vercel/next.js/commit/d23f41c42506005fe6978e076a1ccbf8979e4925";><code>d23f41c</code></a>
 v15.5.12</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/8e75765a6544dc0e6b20aefeade7d33190ffcb7c";><code>8e75765</code></a>
 fix unlock in publish-native</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/6cef992286e3050aeca46e0d506dc5bad4368fd2";><code>6cef992</code></a>
 [backport] normalize CRLF line endings in jscodeshift tests on Windows (<a 
href="https://redirect.github.com/vercel/next.js/issues/8800";>#8800</a>...</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/7a9464553ac72f5b3f3acf17174a61b7b8a210a5";><code>7a94645</code></a>
 Apply needs for publishRelease</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/bbfd4e313d4bc9024ec340d9de419a0e4357f898";><code>bbfd4e3</code></a>
 v15.5.11</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/50060c9adec2b12ffb6ff88ec50a768bb3fad777";><code>50060c9</code></a>
 Unlock swc binaries (<a 
href="https://redirect.github.com/vercel/next.js/issues/89195";>#89195</a>)</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/9599e801e9e633d81bfffa942386a271e6bd0603";><code>9599e80</code></a>
 [backport]: Tracing: Fix memory leak in span map (<a 
href="https://redirect.github.com/vercel/next.js/issues/85529";>#85529</a>) (<a 
href="https://redirect.github.com/vercel/next.js/issues/89135";>#89135</a>)</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/a2e29009515d880011acdbe0e380ae409074953d";><code>a2e2900</code></a>
 [backport]: fix: ensure LRU cache items have minimum size of 1 to prevent 
unb...</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/a2b10ab08cb823053591cd449d8a4801e0b2924c";><code>a2b10ab</code></a>
 [backport] Turbopack: fix NFT tracing of sharp 0.34 (<a 
href="https://redirect.github.com/vercel/next.js/issues/82340";>#82340</a>) (<a 
href="https://redirect.github.com/vercel/next.js/issues/89151";>#89151</a>)</li>
   <li><a 
href="https://github.com/vercel/next.js/commit/662f641285f67ac871eb8f1f44ad0040ea153a26";><code>662f641</code></a>
 [backport] Turbopack: support pattern into exports field (<a 
href="https://redirect.github.com/vercel/next.js/issues/82757";>#82757</a>) (<a 
href="https://redirect.github.com/vercel/next.js/issues/89150";>#89150</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/vercel/next.js/compare/v15.2.1...v15.5.12";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=next&package-manager=npm_and_yarn&previous-version=15.2.1&new-version=15.5.12)](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)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/doris-opentelemetry-demo/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: [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