Skip to content

deps: update next to 16.4.3 and align eslint-config-next - #9

Merged
PsiACE merged 3 commits into
mainfrom
deps/landing-next-16.4.2
Nov 2, 2026
Merged

PsiACE merged 3 commits into
mainfrom
deps/landing-next-16.4.2

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Update next 16.1.6 → 16.4.3, aligned eslint-config-next

Draft candidate refreshed from next 16.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: next stays an exact pin, eslint-config-next stays a caret range in step with it.

Why

next@16.1.6 on main (70f4921) carries advisories that are fixed in later 16.x releases. Dependabot alerts are enabled for this repository but GET /dependabot/alerts?state=open, ?state=dismissed and ?state=fixed all return [], so pnpm audit is the exposure signal here; no alert is closed, dismissed or claimed closed by this PR.

pnpm audit totals (pnpm audit --json, full tree):

Revision critical high moderate low
main 70f4921 4 46 31 5
this head 955623a 0 27 13 1

All next advisories (38 moderate + 4 critical) and the sharp advisories (3 high) are gone at this head (sharp 0.34.5 → 0.35.5, postcss 8.4.31 → 8.5.23). The remaining advisories are pre-existing on main and 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, and zod.

Residual exposure outside this candidate's scope: zod is a production dependency (^3.24.1 → 3.25.76) flagged high, patched only in 4.6.6+. That is a major upgrade which also needs @hookform/resolvers v5+ and app-side changes, so it is neither a pin bump nor covered by an existing candidate.

Changes vs main

  • next: 16.1.6 → 16.4.3 (exact pin preserved)
  • eslint-config-next: ^16.1.6 → ^16.4.3 (caret preserved, kept in step with next)
  • pnpm-lock.yaml regenerated with pnpm 10.34.9; transitive moves: @next/* and all @next/swc-* platform packages 16.4.3, semver 7.7.4 → 7.8.5, postcss 8.4.31 → 8.5.23, sharp 0.34.5 → 0.35.5, eslint-plugin-react-hooks 7.0.1 → 7.1.1; @emnapi/runtime@1.8.1 deduped away
  • next-env.d.ts was regenerated by next build on the previous head and is unchanged by this rebuild

The refresh commit (955623a) on top of the previous head changes only next 16.4.2 → 16.4.3, eslint-config-next 16.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 — pass
  • pnpm build — pass (▲ Next.js 16.4.3, ✓ Compiled successfully, 3/3 static pages generated)
  • pnpm lint — 3 errors, not present on main: react-hooks/set-state-in-effect in components/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. lint is not part of dependency-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 checks dispatched with gh workflow run dependency-checks.yml --ref deps/landing-next-16.4.2:

  • run 40289264306, event workflow_dispatch, head 955623a9e971d597ff3fbd309cffba0ea0cacecf — success (job build: pnpm 10 + Node 20, pnpm install --frozen-lockfile + pnpm build)
  • the pull_request-triggered run on the same head (40289141656) sits at action_required, as for the other bot-authored dependency drafts; the dispatched run above is the authoritative check result

This PR stays a draft; merge remains with the reviewers.

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.
@vercel

vercel Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
v0-tape-systems Ready Ready Preview, v0 Nov 2, 2026 4:48pm UTC

@github-actions

Copy link
Copy Markdown
Contributor Author

Independent CI for head 7e0d5a64: Dependency checks run 39379681446 — success (pnpm install --frozen-lockfile + pnpm build, Node 20 / pnpm 10).

The pull_request-triggered run for this branch is parked in action_required (the repository requires approval for workflow runs pushed by this actor), so the dispatched run above is the CI evidence for this head.

@github-actions github-actions Bot changed the title deps: update next to 16.4.2 and align eslint-config-next deps: update next to 16.4.3 and align eslint-config-next Oct 26, 2026
@PsiACE
PsiACE marked this pull request as ready for review November 2, 2026 16:36

@PsiACE PsiACE left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 build static export, and explicit tsc --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 lint still reports the 3 existing-source react-hooks/set-state-in-effect patterns (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.

@PsiACE
PsiACE merged commit 79252c7 into main Nov 2, 2026
3 checks passed

This branch was successfully deployed

1 active deployment
Preview — ddb6cf93 Deployed Nov 2, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant