dependabot[bot] opened a new pull request, #634: URL: https://github.com/apache/burr/pull/634
Bumps [next](https://github.com/vercel/next.js) from 14.2.14 to 16.1.3. <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>v16.1.3</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>Fix linked list bug in LRU deleteFromLru (<a href="https://redirect.github.com/vercel/next.js/issues/88652";>#88652</a>)</li> <li>Fix relative same host redirects in node middleware (<a href="https://redirect.github.com/vercel/next.js/issues/88253";>#88253</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/acdlite";><code>@acdlite</code></a> and <a href="https://github.com/ijjk";><code>@ijjk</code></a> for helping!</p> <h2>v16.1.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>Turbopack: Update to swc_core v50.2.3 (<a href="https://redirect.github.com/vercel/next.js/issues/87841";>#87841</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/88296";>#88296</a>) <ul> <li>Fixes a crash when processing mdx files with multibyte characters. (<a href="https://redirect.github.com/vercel/next.js/issues/87713";>#87713</a>)</li> </ul> </li> <li>Turbopack: <a href="https://microsoft.github.io/mimalloc/";>mimalloc</a> upgrade and enabling it on musl (<a href="https://redirect.github.com/vercel/next.js/issues/88503";>#88503</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/87815";>#87815</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/88426";>#88426</a>) <ul> <li>Fixes <a href="https://redirect.github.com/vercel/next.js/pull/88426";>a significant performance issue</a> on musl-based Linux distributions (e.g. Alpine in Docker) related to musl's allocator.</li> <li>Other platforms have always used mimalloc, but we previously did not use mimalloc on musl because of compilation issues that have since been resolved.</li> </ul> </li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/mischnic";><code>@mischnic</code></a> for helping!</p> <h2>v16.1.1</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>Turbopack: Create junction points instead of symlinks on Windows (<a href="https://redirect.github.com/vercel/next.js/issues/87606";>#87606</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/sokra";><code>@sokra</code></a> and <a href="https://github.com/ztanner";><code>@ztanner</code></a> for helping!</p> <h2>v16.1.1-canary.32</h2> <h3>Core Changes</h3> <ul> <li>fix: setImmediate[util.promisify.custom] access fails in edge runtime: <a href="https://redirect.github.com/vercel/next.js/issues/88685";>#88685</a></li> <li>Fix <code>--debug-build-paths</code> bracket escaping for glob patterns: <a href="https://redirect.github.com/vercel/next.js/issues/88660";>#88660</a></li> </ul> <h3>Misc Changes</h3> <ul> <li>[turbopack] Add bundling support for worker_threads: <a href="https://redirect.github.com/vercel/next.js/issues/87746";>#87746</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/f01cf07ab12a37259de42baa4bdae310b4328c72";><code>f01cf07</code></a> v16.1.3</li> <li><a href="https://github.com/vercel/next.js/commit/74b43aec65f645185c9e930ae625bd6d8d9b21cf";><code>74b43ae</code></a> [backport]: Fix linked list bug in LRU deleteFromLru (<a href="https://redirect.github.com/vercel/next.js/issues/88652";>#88652</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/812cd757fcdc68c9fc69d35800f72a0710f956b6";><code>812cd75</code></a> [backport] Fix relative same host redirects in node middleware <a href="https://redirect.github.com/vercel/next.js/issues/88253";>#88253</a> (<a href="https://redirect.github.com/vercel/next.js/issues/88630";>#88630</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/cb436b3613edb3f741a39fa00ac31d103a5a1518";><code>cb436b3</code></a> v16.1.2</li> <li><a href="https://github.com/vercel/next.js/commit/e13100a790fb042e77060423b283bf5e7e65e5d1";><code>e13100a</code></a> [Backport] mimalloc upgrade and enabling it on musl (<a href="https://redirect.github.com/vercel/next.js/issues/88503";>#88503</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/beb3a766a9faa103137c7a36e6f13454e27f0c48";><code>beb3a76</code></a> Backport: fix: normalize CRLF line endings in jscodeshift tests on Windows <a href="https://redirect.github.com/vercel/next.js/issues/8";>#8</a>...</li> <li><a href="https://github.com/vercel/next.js/commit/da37eeebffb73c0aa5434e2b706325b9c506d242";><code>da37eee</code></a> Backport (16.1.x): Turbopack: Update to swc_core v50.2.3 (<a href="https://redirect.github.com/vercel/next.js/issues/87841";>#87841</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/88296";>#88296</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/3aa53984e9d6bc4b5860c76e90cccfd6780989af";><code>3aa5398</code></a> v16.1.1</li> <li><a href="https://github.com/vercel/next.js/commit/d1bd5b58104021e6a361cf835233503c3cfed7e0";><code>d1bd5b5</code></a> Turbopack: Create junction points instead of symlinks on Windows (<a href="https://redirect.github.com/vercel/next.js/issues/87606";>#87606</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/a67ee727888e2db716852b4f9c61d6c799d43cfb";><code>a67ee72</code></a> setup release branch</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v14.2.14...v16.1.3";>compare view</a></li> </ul> </details> <br /> [](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/burr/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]
