Repository navigation
deps: update next to 16.4.3 and align eslint-config-next - #9
Conversation
next 16.1.6 is affected by advisories patched in later 16.x releases, including two critical RCE advisories (patched 16.3.3) and App Router SSRF/DoS advisories (patched up to 16.3.8). 16.4.2 also pulls patched transitive postcss (8.5.23) and sharp (0.35.5). Exact pin on next and the caret range on eslint-config-next are preserved.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Independent CI for head The |
There was a problem hiding this comment.
Reviewed original 955623a and updated integration head ddb6cf9. Merged current main (#10) into this branch, resolved the overlapping lockfile from main's refreshed lock, and kept next / resolved eslint-config-next aligned at 16.4.3. Manifest changes remain exactly the intended two version updates; existing caret/exact styles are preserved. Dependency re-resolution includes the corresponding Next/Sharp and ESLint dependency trees; no app source changes.
Validation repeated on the final integrated head (Node 22.22.3 / pnpm 10.34.9):
pnpm install --frozen-lockfile,pnpm buildstatic export, and explicittsc --noEmit: pass.- 16/16 full-page Chromium screenshots with no perceptible visual difference (pixelmatch threshold 0.1) versus pre-upgrade main 70f4921: widths 1440 / 768 / 390 / 320 × EN/ZH × light/dark CSS class. Text, section/heading geometry, links and all 35 SVGs match; no new horizontal overflow.
- Mouse/keyboard language switching, CTA, section navigation, sticky nav and return-to-top: pass on the applicable widths; no runtime/hydration errors or failed page assets.
- Vercel-only analytics script is absent on static localhost baseline and stubbed identically in both test runs; app code is unchanged.
pnpm lintstill reports the 3 existing-sourcereact-hooks/set-state-in-effectpatterns (carousel / two mobile hooks) exposed by the upgraded lint configuration. This was newly failing versus original main, already recorded in #10, not a runtime/UI regression. No suppression added.
Updated-head Dependency checks and Vercel preview are green. Approved under the requested UI/UX merge criterion.
Raw RGBA comparison note: a few rounded-border anti-aliasing channels in the language button differ by at most 1/255; layout is identical and significant-difference pixels are zero. This is visual equivalence, not a claim of byte-identical PNGs.
Update
next16.1.6 → 16.4.3, alignedeslint-config-nextDraft candidate refreshed from
next16.4.2 to 16.4.3, the current latest in the 16.x line (published 2026-10-23, after the previous head 7e0d5a6). Pinning style preserved:nextstays an exact pin,eslint-config-nextstays a caret range in step with it.Why
next@16.1.6onmain(70f4921) carries advisories that are fixed in later 16.x releases. Dependabot alerts are enabled for this repository butGET /dependabot/alerts?state=open,?state=dismissedand?state=fixedall return[], sopnpm auditis the exposure signal here; no alert is closed, dismissed or claimed closed by this PR.pnpm audittotals (pnpm audit --json, full tree):main70f4921All
nextadvisories (38 moderate + 4 critical) and thesharpadvisories (3 high) are gone at this head (sharp0.34.5 → 0.35.5,postcss8.4.31 → 8.5.23). The remaining advisories are pre-existing onmainand unchanged by this candidate:browserslist,lodash,nanoid,flatted,source-map-js,postcss(8.5.8 instance),brace-expansion,picomatch,js-yaml,@babel/core,@humanfs/node,baseline-browser-mapping, andzod.Residual exposure outside this candidate's scope:
zodis a production dependency (^3.24.1→ 3.25.76) flagged high, patched only in4.6.6+. That is a major upgrade which also needs@hookform/resolversv5+ and app-side changes, so it is neither a pin bump nor covered by an existing candidate.Changes vs
mainnext:16.1.6→16.4.3(exact pin preserved)eslint-config-next:^16.1.6→^16.4.3(caret preserved, kept in step withnext)pnpm-lock.yamlregenerated with pnpm 10.34.9; transitive moves:@next/*and all@next/swc-*platform packages16.4.3,semver7.7.4→7.8.5,postcss8.4.31→8.5.23,sharp0.34.5→0.35.5,eslint-plugin-react-hooks7.0.1→7.1.1;@emnapi/runtime@1.8.1deduped awaynext-env.d.tswas regenerated bynext buildon the previous head and is unchanged by this rebuildThe refresh commit (955623a) on top of the previous head changes only
next16.4.2 → 16.4.3,eslint-config-next16.4.2 → 16.4.3 and their lockfile entries.Validation (local, pnpm 10.34.9 / Node 20.20.2, isolated worktree)
pnpm install --frozen-lockfile— passpnpm build— pass (▲ Next.js 16.4.3,✓ Compiled successfully, 3/3 static pages generated)pnpm lint— 3 errors, not present onmain:react-hooks/set-state-in-effectincomponents/ui/carousel.tsx:98,components/ui/use-mobile.tsx:14,hooks/use-mobile.ts:14.main(eslint-config-next 16.1.6) exits 0; the previous head (16.4.2) already fails with the same 3 errors, so this comes from the 16.4.x rule set rather than from 16.4.3.lintis not part ofdependency-checks.yml, so no CI check is affected and no source change is made here; the errors are pre-existing code patterns surfaced by the newer lint config.CI
Independent
Dependency checksdispatched withgh workflow run dependency-checks.yml --ref deps/landing-next-16.4.2:workflow_dispatch, head955623a9e971d597ff3fbd309cffba0ea0cacecf— success (jobbuild: pnpm 10 + Node 20,pnpm install --frozen-lockfile+pnpm build)pull_request-triggered run on the same head (40289141656) sits ataction_required, as for the other bot-authored dependency drafts; the dispatched run above is the authoritative check resultThis PR stays a draft; merge remains with the reviewers.