github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 12:55:03 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[PR #2050] [CLOSED] Bump next from 15.5.7 to 16.0.10 #9624

New Issue
Closed
opened 2026-04-30 05:48:27 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 05:48:27 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/2050
Author: @dependabot[bot]
Created: 12/12/2025
Status: ❌ Closed

Base: main ← Head: dependabot/npm_and_yarn/next-16.0.10

📝 Commits (1)

  • 016df5a Bump next from 15.5.7 to 16.0.10

📊 Changes

2 files changed (+43 additions, -43 deletions)

View changed files

📝 package-lock.json (+42 -42)
📝 package.json (+1 -1)

📄 Description

Bumps next from 15.5.7 to 16.0.10.

Release notes

Sourced from next's releases.

v16.0.10

Please see the Next.js Security Update for information about this security patch.

v16.0.8

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Update react version in cna templates (#86950)

Credits

Huge thanks to @​huozhi for helping!

v16.0.7

Please see CVE-2025-66478 for additional details about this release.

v16.0.6

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • bump the browserslist version to silence a warning in CI (#86625)

Credits

Huge thanks to @​lukesandberg for helping!

v16.0.5

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • fix(nodejs-middleware): await for body cloning to be properly finalized (#85418)

Credits

Huge thanks to @​lucasadrianof for helping!

v16.0.4

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • fix: Rename proxy.js to middleware.js in NFT file (#86214)
  • fix: prevent fetch abort errors propagating to user error boundaries (#86277)

... (truncated)

Commits

Dependabot compatibility score

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 commands and options

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)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fosrl/pangolin/pull/2050 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 12/12/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/next-16.0.10` --- ### 📝 Commits (1) - [`016df5a`](https://github.com/fosrl/pangolin/commit/016df5aaf5b295e9eda78a236269b0c3ada5a4b9) Bump next from 15.5.7 to 16.0.10 ### 📊 Changes **2 files changed** (+43 additions, -43 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+42 -42) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [next](https://github.com/vercel/next.js) from 15.5.7 to 16.0.10. <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.0.10</h2> <p>Please see the <a href="https://nextjs.org/blog/security-update-2025-12-11">Next.js Security Update</a> for information about this security patch.</p> <h2>v16.0.8</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>Update react version in cna templates (<a href="https://redirect.github.com/vercel/next.js/issues/86950">#86950</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/huozhi"><code>@​huozhi</code></a> for helping!</p> <h2>v16.0.7</h2> <p>Please see <a href="https://nextjs.org/blog/CVE-2025-66478">CVE-2025-66478</a> for additional details about this release.</p> <h2>v16.0.6</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>bump the browserslist version to silence a warning in CI (<a href="https://redirect.github.com/vercel/next.js/issues/86625">#86625</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/lukesandberg"><code>@​lukesandberg</code></a> for helping!</p> <h2>v16.0.5</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(nodejs-middleware): await for body cloning to be properly finalized (<a href="https://redirect.github.com/vercel/next.js/issues/85418">#85418</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/lucasadrianof"><code>@​lucasadrianof</code></a> for helping!</p> <h2>v16.0.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>fix: Rename proxy.js to middleware.js in NFT file (<a href="https://redirect.github.com/vercel/next.js/issues/86214">#86214</a>)</li> <li>fix: prevent fetch abort errors propagating to user error boundaries (<a href="https://redirect.github.com/vercel/next.js/issues/86277">#86277</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/581dee67e280b96c0766172cbd5477102c03342b"><code>581dee6</code></a> v16.0.10</li> <li><a href="https://github.com/vercel/next.js/commit/9a0dc9c55582c1936fa2b0df36cff16518a8d126"><code>9a0dc9c</code></a> Backport <a href="https://redirect.github.com/facebook/react/issues/35351">facebook/react#35351</a> for 16.0.9 (<a href="https://redirect.github.com/vercel/next.js/issues/87085">#87085</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/3f6a39f6f75781f16e1cae0b122ae86150f375be"><code>3f6a39f</code></a> v16.0.9</li> <li><a href="https://github.com/vercel/next.js/commit/75e136ad1e90949ba0e8288bdd1e03a52ecc2b7f"><code>75e136a</code></a> Update React Versions (<a href="https://redirect.github.com/vercel/next.js/issues/40">#40</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/4e20596af880838bf6c40fc235e639b142116a7d"><code>4e20596</code></a> Update React Version (<a href="https://redirect.github.com/vercel/next.js/issues/22">#22</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/fa858489446628dfe9387c54078ebb1de1fbd243"><code>fa85848</code></a> Backport Next.js changes to v16.0.9 (<a href="https://redirect.github.com/vercel/next.js/issues/20">#20</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/817ee56da939545d4b77cc54542f4c45a524e60a"><code>817ee56</code></a> v16.0.8</li> <li><a href="https://github.com/vercel/next.js/commit/b298173dba914e55bc25aa6bdc37d418d587830e"><code>b298173</code></a> Update react version in cna templates (<a href="https://redirect.github.com/vercel/next.js/issues/86950">#86950</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/7492122a3bbc6655b64ccba04076c73ab418cdcc"><code>7492122</code></a> v16.0.7</li> <li><a href="https://github.com/vercel/next.js/commit/d21259d920f666814fa634e744d2c6e797ceae43"><code>d21259d</code></a> update version script</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v15.5.7...v16.0.10">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.5.7&new-version=16.0.10)](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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-30 05:48:27 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#9624
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?