chore(deps): bump next from 16.2.10 to 16.3.3 - #36
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.2.10 to 16.3.3. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.2.10...v16.3.3) --- updated-dependencies: - dependency-name: next dependency-version: 16.3.3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
requested review from
fanhousanbu and
jhfnetboy
as code owners
September 11, 2026 02:58
clestons
approved these changes
Sep 11, 2026
clestons
left a comment
There was a problem hiding this comment.
✅ APPROVE — #36 · 建议优先合并
Head: ee6b7b1 · dependabot · next 16.2.10 → 16.3.3 · 2 文件 +284/−222(lockfile 为主)
轮次: 2-round(纯依赖升级)· R1a+R1b DeepSeek → 判断由执行者做
作者意图(一句话):把 Next.js 升到 16.3.3。顺带修掉了仓库里唯一一个 critical 漏洞。
为什么建议优先合它
main 上的 next@16.2.10 落在 npm audit 报的 critical 区间 9.3.4-canary.0 – 16.3.2 里(中间件/Proxy 绕过、Server Actions SSRF、响应体缓存混淆等)。实测对比同一时间的两次 CI:
| 漏洞数 | critical | Security Audit | |
|---|---|---|---|
| #35(仍是 next 16.2.10) | 16(3 moderate / 12 high / 1 critical) | 1(next) | ❌ |
| #36(next 16.3.3) | 13(4 moderate / 9 high) | 0 | ✅ |
--audit-level=critical 的门槛下,这个 PR 让 Security Audit 从红变绿;其余 PR(例如 #35)的红灯也都来自这同一个 next。
核过的
- integrity 与官方 registry 逐字一致:
next@16.3.3lockfile 里的sha512-tuRTx1nQ…=registry.npmjs.org的dist.integrity。 - 换源:改到的 41 个条目
resolved都从registry.npmmirror.com换成了registry.npmjs.org(integrity 行 −40/+40 同步更新)。integrity 是内容哈希,与下载源无关,上一条一致就说明没有夹带;lockfile 因此是混合源,不影响安装。 - Node 版本:next 16.3.3 要求
node >=20.9.0(其依赖sharp同样)。仓库的.nvmrc与Dockerfile(node:20.19.0-alpine)都是 20.19.0,CI 的node-version: "20"取最新 20.x —— 全部满足。 - CI:Build(aastar / aastar-frontend)、Code Quality、CodeQL(JS / TS)、Security Audit、CI Success 全绿。
一处值得知道(不阻塞)
lockfile 里 postcss 的 dev: true 标记没了 —— next 16.3 在运行时依赖它,所以它从开发依赖变成了生产依赖树的一部分。符合预期,只是镜像体积会多一点点。
结论
APPROVE,建议先于其它 PR 合并 —— 它是修掉 critical 的那一个。
Contributor
Author
|
Superseded by #37. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps next from 16.2.10 to 16.3.3.
Release notes
Sourced from next's releases.
... (truncated)
Commits
a9a1cb7v16.3.3968b9fc[16.3.x] Fix ISR misses with backslashes in segments when deployed on Windows3a15b4a[16.3.x] [next/image]: disable avif image optimization7378b51Backport/docs fixes 16.3 (#97649)528c1cd[16.3.x] Stop generating error codes (#97780)d0ac882v16.3.281deb92[16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static ...cd714d9[16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)5ac2327[16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)0ccb3e7[16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.